1) I have been using AXIS2's JAVA2WSDL functionality and all was going well but had some issues when I tried to use the WSDL it generated into other programs for use. It seems that its not generating a "compliant" WSDL. When I imported the generated WSDL into XMLSpy just to validate it, it found a bunch of errors. Most of the problems there had to do with the MIME parts not being named correctly. What has been everyones experience in using the WSDLs generated into other programs. Any issues?
2) Another issue which came up was in the matter of dealing with methods that didnt have any args. For example, if I had a java method: int getValue(); The WSDL created an "empty" operation for getValue(). So, when I then used this WSDL in a program like SoapUI to generate a soap request, the body of the SOAP message was EMPTY. The SOAP Header had the SOAPAction of "getValue" specified, but, it seems that the SOAP body should still have some indication of the operation being performed. Why is there no method signature for a no-arg method call? How do I get one in using JAVA2WSDL? I hope this is making sense to someone out there... Thanks, Marc -- View this message in context: http://www.nabble.com/JAVA2wsdl-problems-tp15494027p15494027.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
