You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/04/17 19:55:01 UTC

DO NOT REPLY [Bug 19123] New: - Java2WSDL docs slightly misleading about getting parameter names from .class file

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=19123>.
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=19123

Java2WSDL docs slightly misleading about getting parameter names from .class file

           Summary: Java2WSDL docs slightly misleading about getting
                    parameter names from .class file
           Product: Axis
           Version: 1.1rc2
          Platform: All
               URL: http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-
                    axis/java/docs/user-
                    guide.html#Java2WSDL:%20Building%20WSDL%20from%20Java
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Documentation
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: srowen@yahoo.com


The Java2WSDL documentation says that to generate a WSDL from a Java source
file, one should:

"Write and compile a Java interface (or class) that describes the web service
interface.... (example) ... Note: If you compile your class with debug
information, Java2WSDL will use the debug information to obtain the method
parameter names."

Java only puts method parameter names into .class files for compiled classes
(not interfaces), and only then for non-abstract methods. So Axis can only get
method parameter names in certain situations.

I know that Java2WSDL has an "-i" option that lets one specify an implementation
class for an interface being processed, from which to extract method parameter
names.

So, I'd just suggest qualifying the comment above, and maybe noting what the
user must do to get method parameter names when generating a WSDL from an
interface; it may save a little head-scratching.