[JBoss-user] [JBoss.NET SOAP] - Re: Cannot deserialise JavaBeans

2004-06-10 Thread bensorek
I had the same problem, but i didn't hack the wsdl. However in the client code the qname i would use for the SimpleDto is: http://com/cdog/service/SimpleService:SimpleDto and not SimpleService:SimpleDto. For some reason that worked! View the original post :

[JBoss-user] [JBoss.NET SOAP] - Re: Cannot deserialise JavaBeans

2004-05-18 Thread cdog
Hi, Thanks for that Scott. I seem to have got a bit further. I've hacked the wsdl as suggested and this has got rid of the previous error, but now I'm getting a bad type error. I've included the hacked wsdl and the error at the end of this post. You can see from the error that the

[JBoss-user] [JBoss.NET SOAP] - Re: Cannot deserialise JavaBeans

2004-05-17 Thread Takenori
Hi, Do you include your SimpleDto in ejbDoclet task? This is one of the most common error. Takenori, View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3835202#3835202 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3835202

[JBoss-user] [JBoss.NET SOAP] - Re: Cannot deserialise JavaBeans

2004-05-17 Thread cdog
Hi, I'm pretty sure it is included OK. The typeMapping element for the SimpleDto in the web-service.xml is generated by Xdoclet. I checked by removing the fileset that referenced to the SimpleDto this resulted in the typeMapping element is not being included in the web-service.xml. View the

[JBoss-user] [JBoss.NET SOAP] - Re: Cannot deserialise JavaBeans

2004-05-17 Thread [EMAIL PROTECTED]
The wsdl file generated by the axis servlet incorrectly includes types from all deployments. You can see that the SimpleDto exists under two different namespaces, and the client generation happened to choose the wrong one. Cleanup the wsdl by hand and re-run the code generation. View the