Hi!
What kind of client are you using?
Have you tried to use soapUI to send requests to the web service and examine the result?
If using soapUI does not work, then there is a problem with your web service.
If soapUI does work, but your client does not work, then the problem is most likely to be the client.
Best wishes!
Ivan Krizsan wrote:Hi!
What kind of client are you using?
Have you tried to use soapUI to send requests to the web service and examine the result?
If using soapUI does not work, then there is a problem with your web service.
If soapUI does work, but your client does not work, then the problem is most likely to be the client.
Best wishes!
Hi.
I tried soapUI with my small "learning-project". It is able to send a request, and it gets a response (the same works with my java me client). But just as described in this thread, when it reaches the server, the arguments are somehow lost.
Alex Parvan wrote:I found my problem, for some reason, i have to write all elements inside a schema and import that.
Thanks for sharing this. However, to me, it sounds strange - you should not have to do that. It should be possible to declare the message types in the <types> element of the WSDL.
An advice when writing a WSDL by hand is to use the WS-I Compliance Check tool to verify the correctness of the WSDL a step further than basic XML validation is able to do. Instructions here: http://www.soapui.org/userguide/tools/wsi.html Best wishes!
Mattias Sands�ter wrote:
I tried soapUI with my small "learning-project". It is able to send a request, and it gets a response (the same works with my java me client). But just as described in this thread, when it reaches the server, the arguments are somehow lost.
Please do not hijack threads - you have already posted this question in another thread and once is enough.
Best wishes!
Post by:autobot
Your mother was a hamster and your father was a tiny ad:
a bit of art, as a gift, that will fit in a stocking