jackdawson wrote: > > Hello all, > I found something bizarre which made to wonder why. > > Here is what I found: > 1.) When I used Axis2 Eclipse Codegen plugins (Generate Java > source code from WSDL file) to generate code from this WSDL, it didn't > allow me. > It kept throwing me an error - > "An error occurred while completing the process - > java.lang.InterruptedException > No element type is defind for the message xxxxx" > 2.) Then, I switched to CXF 2.0.8 and tried to generate the client > as I did with Axis2 and surprisingly, it got through and created the > client side stubs. > CXF doesn't see this WSDL as a bad one. > > ...snip... >
These questions might be better suited for the Axis mailing list. Axis2 is not a pure JAX-WS implementation, so they may process a WSDL differently. I think whether the JAX-WS objects are generated in doc/lit or rpc/lit format is defined by the wsdl:binding section, not by message attribute values. Glen -- View this message in context: http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-tp19696717p19708707.html Sent from the cxf-user mailing list archive at Nabble.com.
