After some investigation (commenting out and uncommenting out sections of WSDL)-- I've determined the cause of the problem.
If a doc/literal wrapped WSDL uses xsd:any in the wrapped request or response type, then the WSDL2Java tool will generate the interface with style SOAPBinding.ParameterStyle.BARE. I don't believe this is the intended behavior (is it?) and have submitted a bug report (with example code/wsdl): https://issues.apache.org/jira/browse/CXF-502 At this point, this is a stopper for me porting my service from XFire to CXF. Once the bug is resolved, I'll give it another shot. Thanks, Chris -----Original Message----- From: James Mao [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 10:05 AM To: [email protected] Subject: Re: Wsdl2Java Generating BARE not WRAPPED Hi Chris, I suggest you open the validate option, to check if there is any errors/warnings during processing. And also you can try the JAXWS RI, and see if generated as you expected. The last option, also the quickest option is fire an issue on [1] , attach your wsdl. [1] https://issues.apache.org/jira/browse/CXF Thanks, James. > I'm using the Maven 2 plugin for executing Wsdl2Java. Although my WSDL > is in doc/literal wrapped style, the generated code specifies > SOAPBinding.ParameterStyle.BARE. And the style of the generated methods > is also bare-for example: > > > > @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) > > @WebResult(targetNamespace = "http://mycompany.com/ws";, partName = > "body", name = "MyOperationResponse") > > @WebMethod(operationName = "MyOperation") > > public com.mycompany.ws.MyOperationResponseType myOperation( > > @WebParam(targetNamespace = "http://mycompany.com/ws";, partName > = "body", name = "MyOperation") > > com.mycompany.ws.MyOperationType body > > ); > > > > If I run the same WSDL through the XFire 1.2.5 generator, it correctly > identifies it as doc/literal wrapped and generates code in that style. > So I suspect my WSDL is correct. > > > > I didn't see any open issues regarding this-is anyone else having > problems with it? Any suggestions for things I might try? Any gotchas > between how XFire identifies wrapped style and how CXF identifies it? > > > > Thanks, > > Chris > > > > > > >
