The relationship between Apache SOAP and Axis is similar to that between
JServ and Tomcat. Axis will ultimately be the preferred (and presumably
faster and more feature rich and stable) implementation. However, it is
hard to predict the point at which a critical mass of users will move to
Axis.
I like the idea of generating client code. It has been suggested on the
soap-dev list before, but, to my knowledge, no one has tackled it. An
alternative technique was described in JavaWorld
(http://www.javaworld.com/javaworld/jw-07-2001/jw-0706-soap.html) using
dynamic proxy classes. What I prefer about code generation is that it can
work with older JDKs as well.
I will be interested to see what response you get from the committers for
these projects.
Scott
----- Original Message -----
From: "Henner Zeller" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, July 11, 2001 10:03 AM
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
>
>
>
