You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2002/09/23 22:13:35 UTC
DO NOT REPLY [Bug 12936] New: -
WSDL2Java generates value0, value1 etc. as the static final enumeration constants.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12936>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12936
WSDL2Java generates value0, value1 etc. as the static final enumeration constants.
Summary: WSDL2Java generates value0, value1 etc. as the static
final enumeration constants.
Product: Axis
Version: 1.0-rc1
Platform: Sun
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: WSDL processing
AssignedTo: axis-dev@xml.apache.org
ReportedBy: harishp@mail.finex.com
I defined a simpleType in wsdl that looks something like this:
<xsd:simpleType name="PlanType">
<xsd:restriction base="xsd:int">
<xsd:enumeration name="Gold" value="0"/>
<xsd:enumeration name="Silver" value="1"/>
<xsd:enumeration name="Bronze" value="2"/>
</xsd:restriction>
</xsd:simpleType>
The resulting wsdl2java generated code does not make use of the "Gold",
"Silver", "Bronze". Is there a way I can associate user defined identifiers
within the generated code instead of value0, value1 etc. that get generated
by default.
Although this is not a part of the XML schema spec., but it seems wierd
to deal with static final constants like value0, value1 etc. instead of
Gold, Silver etc.
Harish