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
