+1 as well. A -bare flag to disable the unwrapping would be cool as well.
On Sat September 26 2009 11:57:03 am Christian Schneider wrote: > +1 for this > > Does anyone know what needs to be tweaked to achieve this? I'd have to dig though a bit to get specifics which I'll do later today while the kids are napping or after they go to bed, but the basics are that you : 1) Add a constant to ToolsConstants 2) Edit tools/wsdlto/frontend/jaxws/src/main/java/org/apache/cxf/tools/wsdlto/frontend/jaxws/jaxws- toolspec.xml to add the flag to the command line parser 3) Probably update something in the jaxws processors, probably OperationProcessor. That's where I would need to dig a bit more. Basically, where we check the binding file for the flag, we would need to also check the ToolContext for the flag. 4) Then update the Options object in the codegen plugin to expose it there. Dan > > Greetings > > Christian > > Glen Mazza schrieb: > > Hello, according to the CXF User's Guide[1] it is necessary to create a > > WSDL binding file in order to direct WSDL2Java to create asynchronous > > versions of the WSDL operations ([2] for example). > > > > Question: Instead of needing to create such a binding file, couldn't CXF > > just provide a WSDL2Java -async or similar setting in order to generate > > the async methods? Axis2 has similar -a/-s settings[3]. > > > > Thanks, > > Glen > > > > [1] > > http://cxf.apache.org/docs/wsdl-to-java.html#WSDLtoJava-JAXWSCustomizatio > >n [2] > > http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samp > >les/jaxws_async/src/demo/hw/client/Client.java?annotate=651669 (lines 62 > > and 73) > > [3] http://ws.apache.org/axis2/tools/1_3/CodegenToolReference.html > -- Daniel Kulp [email protected] http://www.dankulp.com/blog
