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>
</wsdlOptions>
Or just -bareMethods=testManifest if your running wsdl-2-java command-line.
If you have many such methods, create a binding file and set
enableWrapperStyle to true:
https://cwiki.apache.org/CXF20DOC/wsdl-to-java.html#WSDLtoJava-wrapperstyle
will work for all methods. You can attach the binding file to your
wsdl-to-java process via the "-b" setting, or here for the Maven
plugin:
https://cwiki.apache.org/CXF20DOC/maven-cxf-codegen-plugin-wsdl-to-java.html
HTH,
Glen
On 06/12/2012 06:20 AM, santoshkumar wrote:
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", targetNamespace =
"http://soa.mytest.com/test/messages/test1";, className =
"com.mytest.soa.test.messages.test1.TestManifestDocument")
@WebMethod(operationName = "TestManifest", action = "TestManifest")
public void testManifest();
I hope am not any limitation and there might be parameter/args which can
create code gen similar to axis for this case.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Migration-to-CXF-WSDL2Java-is-not-generating-method-with-input-parameter-tp5709568p5709575.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
