Lance, correct me if I'm wrong, but you are working on WSDL2Java
functionality only, correct? (i.e. given a WSDL document, generate Java
proxies.)
As I read Henner's message, he seems to be talking about Java2WSDL type
functionality (given a Java class, render WSDL for it), which I would
personally also love to see.
Jim Moatas (sp?) sent a draft contribution of some java2wsdl code, but no
one made time to look at it, which may have disappointed him to the point
of disappearance. (Jim, you still out there???) I will be taking a gander
at that code later this week, and I may resend it to the list so you and
Henner et al. can take another look at it as well.
Cheers,
Rob
At 10:05 AM 7/11/2001 -0700, KIND,LANCE (HP-FtCollins,ex1) wrote:
>Hen, not to discourage since what I am working on is vapor since it hasn't
>been released, but I am porting a WSDL2 Axis Client proxy (from another
>source base) which I hope to have working with primitive types by the end of
>the week (and damn that end is coming up fast :-().
>
>At any rate, this is just an FYI. Now I had better get back to coding.
>
>Cheers,
>
>==>Lancer---
>
>
>> -----Original Message-----
>> From: Henner Zeller [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, July 11, 2001 7:03 AM
>> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>> Subject: Client Code generator ..
>>
>>
>>
>> Hi,
>> I am in the process of evaluating the apache soap effort and
>> am interested
>> in contributing to it, since I think a feature complete, fast
>> and stable
>> SOAP implementation is as important for the near future as e.g. tomcat
>> already is. I don't know yet, where I should spend my
>> resources, however:
>> xml-soap or axis .. aren't these similar projects ? Axis
>> seems to be the
>> successor of xml-soap, but seems to be in development, thus not widely
>> used yet; is this that sort of relationship like between
>> ApacheJServ and
>> Tomcat ?
>>
>> I think, an interesting sub-project would be to provide a simple
>> application which converts a java interface into a soap client, using
>> the provided mappings from the deployment descriptor. This has two
>> advantages
>>
>> - toolkit independant. You just convert the interface to a generated
>> java class. If the soap-tookit changes, only the code generator
>> changes but you don't have to re-implement all the client
>> classes you
>> (tediously) wrote by hand.
>>
>> - a java interface is IMHO much more readable than a wsdl
>> file .. whose
>> syntax seems still in the flux btw. In the second phase,
>> generating
>> a client class from a wsdl file is of course desirable as well.
>>
>> If this isn't implemented somewhere, I'd just go ahead an
>> implement it..
>>
>> by,
>> -hen
>>
>>
>
>
>Attachment Converted: "d:\robj\eudora\attach\KIND,LANCE
(HP-FtCollins,ex1)10.vcf"
>
