Incomplete code generation with wsdl2java, in adb mode
------------------------------------------------------
Key: AXIS2-2755
URL: https://issues.apache.org/jira/browse/AXIS2-2755
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: wsdl
Affects Versions: 1.2
Reporter: Stephane Roy
The XSD schema used by my WSDL defines the following types:
...
<xsd:complexType name="typeA">
<xsd:sequence>
<xsd:element name="typeB">
<xsd:simpleType>
<xsd:restriction base="xsd:positiveInteger">
<xsd:minExclusive value="01"/>
<xsd:maxInclusive value="99"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
...
In short, typeA uses typeB, typeB being defined within typeA.
I generate the code for the server in adb mode with the command
$AXIS2_HOME/bin/wsdl2java.sh -uri myService.wsdl -p my.package -o
/tmp/my/dir/server -d adb -s -wv 1.1 -ss -sd
Then in /tmp/my/dir/server/src, I have a java file for typeB, for which the
package name is not set ('package ;'). As a result, the java code cannot be
compiled.
I have this problem with Axis2.1.1.1 and with the latest release (Axis2.1.2).
However, if I change my XSD schema, to have something like this:
...
<xsd:simpleType name="typeB">
<xsd:restriction base="xsd:positiveInteger">
<xsd:minExclusive value="01"/>
<xsd:maxInclusive value="99"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="typeA">
<xsd:sequence>
<xsd:element name="elementB" type="typeB">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
...
In short, typeB is now defined at the top-level in the XSD schema and typeA
defines elementB which uses a reference to typeB.
Now, the code generation in adb mode works fine and the java files compile.
It would be nice to be able to generate the java code directly without having
to apply a workaround on the XSD schema.
Thanks in advance.
PS: This problem has been submitted to the User mailing list:
http://marc.info/?l=axis-user&m=117880285406963&w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
