As an alternative to this approach, couldn't you use something like CapeClear's WSDL
editor which is capable of generating stub implementations of a Web service? Then you
get WSDL and Web service separation. IMHO, it's a bad idea to rely on auto-generated
WSDL. Because WSDL defines the interface contract, it should not be easy to change.
Such a tool should be trivial to write.
-----Original Message-----
From: Lasker, Kory [mailto:[EMAIL PROTECTED]]
Sent: Fri 4/12/2002 2:56 PM
To: '[EMAIL PROTECTED]'
Cc:
Subject: RE: <wsdl:documentation> support?
I'm not familiar with how Axis parses .jws's, but wouldn't that be
possible since it's uncompiled? Admittedly, allowing this would be a fairly
ugly behavioral quirk in the API. I'd love to be able to just setup the
Deployment Descriptor with the Java/Javadoc path and have it work though.
Keep it in mind at least. ;)
Kory Lasker
-----Original Message-----
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 12, 2002 4:35 PM
To: [EMAIL PROTECTED]
Subject: Re: <wsdl:documentation> support?
Taking javadoc comments and putting them into WSDL would really be nice.
But it's not easy. Java2WSDL works from .class files. Javadoc comments
aren't in .class files. So Java2WSDL would have to know where to find the
javadocs (or the .java files) and be able to parse them. It's not a
trivial task, so don't expect it any time soon.
Russell Butek
[EMAIL PROTECTED]
"Lasker, Kory" <[EMAIL PROTECTED]> on 04/12/2002 04:19:47 PM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: <wsdl:documentation> support?
Does Axis have anyway to support these documentation elements from the
WSDL 1.1 spec?
I want to be able to leave comments in my classes such that when the wsdl
is created, these notes will be added for the client's benefit.
Axis is quite nice in that client stub generation from a WSDL takes these
comments and inserts them as real comments into the Java code. Handy.
Kory
<<winmail.dat>>
