I am looking at the 'start with wsdl' approach of building a web service. If I follow this approach, I can use either an editor or any tool to build the abstract part of a WSDL - i.e. with no binding or service elements. Ideally, since I have defined the abstract interface I should be able to run a tool to generate the java artifacts and proceed from there.
But the standard WSDL2Java tool does not generate the java interface from the portType information unless a binding element is added to the WSDL. The tool generates complex types that are exchanged in the interface methods correctly, but not the actual interface from the portType. I am looking for any inputs about people's experience with the 'start with WSDL approach'. Should I hand generate a default binding and then use the WSDL2Java and move from there? Or is there any better option? Thanks, Shantanu Sen
