Hello, I am resending this mail as the last time I sent it it was html formatted and I see that that was the wrong format and maybe that is why I saw no responses to it.
Since the posting of this, I am pretty sure the description of the problem identifies a bug, and created http://bugzilla.exolab.org/show_bug.cgi?id=1699 o track this. Cheers Eric Original Mail: We are trying to upgrade our castor from .9.3.9 to .9.5.3 and we seem to have run into a little problem which I am having trouble figuring out an answer to. The generated code for the set/gets is now using the restriction base type instead of the simpleType that was being used before. So we would like to avoid a bunch of code change. There must be somethine that I haven't found yet that controls this. Thanks Eric For the schema that looks like this: <xsd:simpleType name="ChannelProtectionType_T"> <xsd:restriction base="xsd:integer"> <xsd:enumeration value = "CPT_NA" /> <xsd:enumeration value = "CPT_S" /> <xsd:enumeration value = "CPT_P" /> <xsd:enumeration value = "CPT_Y" /> <xsd:enumeration value = "CPT_R" /> </xsd:restriction> </xsd:simpleType> which is used in somethine like this: <xsd:complexType name="LinkConnection_T"> <xsd:sequence> <xsd:element name="aNEId" type="ObjectReference_T"/> <xsd:element name="zNEId" type="ObjectReference_T"/> <xsd:element name="channelProtType" type="ChannelProtectionType_T"/> <xsd:element name="channelServerProtType" type="ChannelServerProtectionType_T"/> </xsd:sequence> <xsd:attributeGroup ref="LinkConnectionAttr"/> </xsd:complexType> used to generate code that looked like this: public abstract class LinkConnection_T implements java.io.Serializable { .
