Hi Glen/Santosh,
I am facing similar issue of getting void methods and no wrapper objects
generated, I am using ant. somehow link
https://cwiki.apache.org/CXF20DOC/wsdl-to-java.html#WSDLtoJava-wrapperstyle
is no more accessible now, looking for workaround, any help in this regard
would be
I am migrating wsdl-java code generation from Axis to CXF. Have hit an issue
with following WSDL which does not generate method with input parameters
with CXF. The same WSDL used with Axis 2 generates the method parameter.
The given WSDL is:
wsdl:definitions
Welcome to CXF. Metro rejects that WSDL outright because it's missing a
wsdl:service and wsdl:binding section, the truncated behavior you're
getting with CXF may also be because you're not using a full WSDL.
(Using my soap_client_tutorial code here:
http://cxf.547215.n5.nabble.com/file/n5709575/TestManifest_Concrete.wsdl
TestManifest_Concrete.wsdl
Even if the concrete part to WSDL ie the service with binding information is
added, CXF still generates method name with empty parameter.
@Oneway
@RequestWrapper(localName = TestManifest,
OK, one way to fix the problem is to use the extraargs parameter below
if you're using Maven:
wsdlOptions
wsdlOption
wsdl
${basedir}/src/main/resources/ShoppingService.wsdl
/wsdl
extraargs
extraarg-bareMethods=testManifest/extraarg
/extraargs
/wsdlOption
