DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7612>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7612 Java2WSDL does not work in some cases ------- Additional Comments From [EMAIL PROTECTED] 2002-04-09 16:29 ------- 1. I assume you mean you tried: Java2WSDL -n urn:my-service ...? Try Java2WSDL -n "urn:my-service" ... The dash is a key symbol in the command line interpreter. Actually, I was using Ant to do it. I passed ant arg as urn:my-service, and it return the usage. I think you are right. I will try with the quote. 2. I don't understand. If you do not specify a SOAPAction, then the SOAPAction is "". I was comparing with WSDL generated from APACH SOAP 2.2 where SoapAction is not "" where Axis generated SoapAction="" by default. I think I am probably comparing Apple and Oranges. 3. How doesn't it work with an EJB Object? Do you have an example and stack traces of failures? I used the EJB stateless sessionbean .java file and passed JAVA2WSDL file and the WSDL was generated has no content, ie. no message, no service, no binding etc. . And there was no error. I guess all these may not real bugs. I probably should take time to understand more about AXIS before I file a bug report. Sorry. I wish there are better documentation. One thing I did noticed: hope this is not a bug, is that if the reponse type is an Integer, WSDL generated has SOAP-ENC encoding style not xsd encoding --> which MS SOAP tool kit does not like. Thanks for looking into these. I promise I will be more careful nexttime I file a bug. Chester
