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 Colin Sampaleanu <co...@exis.com> on 2002/08/08 21:48:21 UTC
Java2WSDL: unable to generate argument names for methods in interfaces
Currently Java2WSDL is unable to generate argument names for methods in
interfaces, due to the fact that javac doesn't actually put out this
information when writing .class files for interfaces (or abstract
methods in normal classes either).
Generating WSDL with proper argument names would be a lot more useful
though, instead of in0, in1, etc.. One way I can see to do it is to
actually parse the source files. The .class files have all the info
needed to locate corresponding source, given a source base directory fed
to Java2WSDL, and the parsing would (I think) be relatively simple.
Does anytbody else think this is useful? Am I missing something?
Re: Java2WSDL: unable to generate argument names for methods in interfaces
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Colin Sampaleanu" <co...@exis.com>
To: <ax...@xml.apache.org>
Sent: Thursday, August 08, 2002 12:48 PM
Subject: Java2WSDL: unable to generate argument names for methods in
interfaces
> Currently Java2WSDL is unable to generate argument names for methods in
> interfaces, due to the fact that javac doesn't actually put out this
> information when writing .class files for interfaces (or abstract
> methods in normal classes either).
>
> Generating WSDL with proper argument names would be a lot more useful
> though, instead of in0, in1, etc.. One way I can see to do it is to
> actually parse the source files. The .class files have all the info
> needed to locate corresponding source, given a source base directory fed
> to Java2WSDL, and the parsing would (I think) be relatively simple.
>
> Does anytbody else think this is useful? Am I missing something?
I wonder if xdoclet (xdoclet.sf.net) could generate the information that is
needed. I wouldnt expect it to be able to do the WSDL directly, but it could
create some XML file containing enough prechewed class information from the
java source to do what you want.
-steve