I figured you deleted your other post because you saw
this one.
Actually I think its actually safer to cobble your own WSDL together (
SOAP attachments with JAX-RPC). Unfortunately that requires some working knowledge of WSDL.
Java2WSDL is OK if you intend to implement Java-to-java RPC over HTTP. If you are truly designing a "SOAP web service" you are better off thinking about the request and response
messages required to get the job done and designing the WSDL first. Then use WSDL2Java.
Unfortunately most platforms invested their effort into code-to-definition generators (it appealed to the "I want to implement web services but can't be bothered to learn about WSDL" crowd) rather than graphical WSDL designers (XML can be a bit hard on the eyes).
So WSDL tools still seem to be mainly in the
commercial domain (the proliferation of WS-* standards makes it somewhat difficult to keep such an editor up to date, even though only a minority of users would need
all of them).
And just because you can create a valid WSDL doesn't mean all platforms (including your own) can deal with it - that's where interoperability comes in.
