Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Java WSDL used by .NET  RSS feed

 
Mat Anthony
Ranch Hand
Posts: 261
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
I have created a WSDL file using org.apache.axis2.wsdl.WSDL2Java.
I have implemented the service side using the generated java skeleton classes.

The aabove WSDL file is used by .NET to generate a proxy client to call the above service.

The service is currently getting the following resonse from the client:- /services/MyService/findPersonID
(i.e. after checking the request defaultRequestURI and firstQueryString)
It should be /services/MyService/findPersonID?personId=1234

Does .NET have a problem reading a WSDL generated from java?, hence the above problem?

I need some help on this
 
Yaron Naveh
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The url of the request is something you can control from the client.

Generally for classic web services the personId should not be in the url but inside the HTTP body. If you are doing something like a web service over GET then I'm not sure the .Net client can handle it directly, maybe you can just send HTTP requests from .Net.
 
Mat Anthony
Ranch Hand
Posts: 261
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Yaron,
If the soap request is in the body, how do I see it if I need to redirect the request from a acegi filtter
to the webservice. I init tested the service as above within the url. Can you see the soap package sent from within the request object?

 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mat Anthony wrote:Hi All,
I have created a WSDL file using org.apache.axis2.wsdl.WSDL2Java.
I have implemented the service side using the generated java skeleton classes.
...
It should be /services/MyService/findPersonID?personId=1234


So are you telling me that you defined a HTTP GET binding inside the WSDL?
Because that is the only way that URL would work. A regular SOAP web service doesn't use query parameters or HTTP GET. All requests are HTTP POSTed to a single endpoint URL, the parameters are always part of the payload in the SOAP envelope that is carried in the HTTP POST request body.

Now it is more likely that your IDE (or a page generated by the IDE) takes that URL and translates it to the actual SOAP call to the endpoint at /services/MyService.

Mind showing the WSDL?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!