I have run into a problem where we generate java classes based on a wcf service wsdl. WCF service works, tested with the soapUI. But in java application, when we sends the requests, it adds one more namespace to a request.
When 'ns5' is removed in soupUI and request is send, it works without problem. Next to that, when we changed the jax-ws attributes in generated classes, targetnamespace, nothing changes.
I was wondering since it works in .Net client, what differs in Java generated classes and how to avoid that ?
Thanks in advance,
I will copy only related parts of the .net service impl. and java generated classes since service is long enough.
To be more concise, wcf service is called by soap java client which is generated by wcf wsdl. WCF service is based on some external web service ETSI Mobile signature standard .
.NET generated class,
a pazwant wrote:Service impl. has changed again and this time by using wsimport java client classes are generated; but still no luck; client request adds a namespace and we get error on serverside. Without it works.
Is the problem generated classes used by wsimport or about the wsdl itself ?
Thanks for you help,