Hello,
Is there some configurability in how the code generation is done? We
generate java classes from a schema that is made available as part of an sdk
for a service. The service routinely adds new enumeration values to types
so that we have to keep re-generating the java classes to match what they
return in queries. Ideally, we would like to configure the code generation
so that when there is some schema that restrict values, we don't want the
restriction to be generated in the Java code so that we don't have to keep
regenerating the java classes. In our case, the values pass through us and
we don't really look at them so that we don't need to deal with the specific
enumeration values.
For example, if there is schema like this:
<xsd:element name="SomeField">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="value1"/>
<xsd:enumeration value="value2"/>
<xsd:enumeration value="value3"/>
<xsd:enumeration value="value4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
We would like to configure the code generation so that the code is generate
as if the schema was:
<xsd:element name="SomeField">
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
If there is some way to configure this in the code generation or if there is
some other way to handle the problem, please let me know.
Len Takeuchi
Salescentrix
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
