You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Bosko Zivaljevic (bzivalje)" <bz...@cisco.com> on 2008/06/03 00:36:10 UTC
Axis2 wsdl2java codegen gives different structures than Axis1
I'm having a problem where I can't get Axis2 to generate a java class so
that it is compabible with how Axis1 generated the java for the same
portion of wsdl.
Specifically, with Axis1 the wsld resulted in generating a primitive
array, but with Axis2 it generates an additional ArrayOf class and then
this new class contains the primative array.
These are the arguments I used in my ant task
<arg line="--databinding-method ${databiding}"/>
<arg line="--server-side ${serverside}"/>
<arg line="-uri ${wsdlfilename}"/>
<arg value="--unpack-classes"/> <!-- This option specifies whether
to unpack the
classes and generate separate
classes for
the databinders. -->
<arg value="--generate-all"/> <!-- Generates all the classes. This
option is
valid only with the -ss (server
side code
generation) option. When on, the
client code
(stubs) will also be generated
along with the
skeleton. -->
<arg value="--all-ports"/> <!-- Generate code for all ports -->
<arg value="--flatten-files"/> <!-- Flattens the generated files -->
<arg value="--sync"/> <!-- Generate code only for sync
style -->
<arg line="-Ejavaversion 1.5"/>
<arg value="--unwrap-params"/> <!-- Switch on un-wrapping -->
<arg value="--noBuildXML"/> <!-- Don't generate the build.xml in
the output directory -->
<arg value="--noWSDL"/> <!-- Don't generate WSDL's in the
resources directory -->
<arg line="--output ${output.generated.src}"/>
<arg value="--backword-compatible" /> <!-- Generate Axis 1.x
backword compatible code. -->
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org