the WSDL generation is a matter of having correct meta-data, i.e., we must have additional information with the
provider class. Axis has such information, but it is neither very well documented nor easy to develop.
Our approach currently is to have a set of reasonable jboss.net-xdoclet extensions and corresponding provider/typemapping implementations that come with a set of alternative meta-data to the Axis ones. We need that, e.g., to determine different XML-Schema views onto the same Java class.
It should be straightforward of extending that to support overloading through mangeling or renaming. You are invited to help us in this respect once we got the new meta-data format checked-in, ok?
Thanks for the reply.
Do i understand it correctly that you plan to create you own meta-data system describing WS? If so, what is the estimated time plan?
Btw have you checked Macromedia Salsa beta development on
http://betaprograms.macromedia.com? They are going to develop "independent" library for interconnection of flash and server via WS, JMX, .... (more or less what runs now with their JRun)