Originally posted by graham king:
Here's the current setup:
JBoss-4.0.5.GA
jbossws-native-2.0.1.GA
jwsdp-2.0
jdk 1.5.0_13-b05
If you have JBossWS why do you also have the JWSDP? Installing JBossWS can't fix anything that may be potentially wrong with the JWSDP - you actually have to use JBossWS instead.
Let me see if I understand your setup: your JBoss server is a web services client to a web service implemented with a Microsoft web service toolkit. Also the client stub being used on the JBoss seems to have no problem assembling the SOAP request - however you now get a SOAP response that indicates that the server has problems with the content of the element with an xsd:anyType data type.
If that is a fair assessment of your situation then your are going to have to take a closer look at the contents of that xsd:anyType element in the SOAP request payload. I'm assuming that the web service itself "is working", i.e. that it can't be a problem on the service server end.
Take a look at the SOAP request that your client stub is sending out. Is the content of the xsd:anyType well formed XML? Even if it is well formed, it could still be invalid with reference to the XML schemas that the server is using.
Remember that the WSDL does not place any specific constraints on the content of xsd:anyType and xsd:any. What is valid inside these elements has to be established outside of the WSDL contract. Therefore the generated code cannot help you to make sure that the content of these elements is in fact something that the web service server can process.
Try to come up with the simplest SOAP request possible (i.e. extremely simple info in the xsd:anyType element) and see if you can get it to work. Once you get it to work, make it more and more complex until you run into problems again - that should give you an idea what needs to be fixed.
At this point I would be inclined to take the application server out of the equation entirely while I'm exploring the client server interaction and simply write a command line program that is using the generated stubs. The JWSDP wscompile creates client stubs that will work outside of an application server and I wouldn't be surprised if JBossWS can do the same thing.