[jboss-user] [JBossWS] - Re: wsconsume - Problems regarding http://www.w3.org/2001/XM
do-not-reply at jboss.com
Tue Sep 11 03:24:38 EDT 2007
Have a look at this... what i have posted
I have also experienced issues like this when generating stubs for clients.
To resolve issues like this even with the newer stack i had to modify wsdl by hand for interoperability.
The way i did is first i created a service and client within Jboss and see how it work and what SOAP packet goes on wire...
Then do a same sort of thing on .NEt side and capture SOAP packet.
Now try to send the SOAP packet what .NET expects, for that you will have to modify your wsdl by hand. Once you know the difference between .NET side generated WSDL and required by Jboss ws client stack you cam modify other WSDLs. Some heavy lifting required to grasp the differences
Mos of the issues i have come across is Because JAX-WS is pretty strict where as older stacks were not that strict in some conventions.
All SOAP toolkit work fine within same envioronment but when used with other you normally have to fiddle with WSDL to make them work. Interoperability is their but with some modifications not just out of box yet.
I hope this helps..
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082859#4082859
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082859
More information about the jboss-user