1. Hopefully no one is working on the list feature, if there is let me
know. I don't want to be repeating someones work.
2. The List feature appears to be already almost implemented but
implemented in a way that doesn't follow the JAXB spec?
There is a ListType on the schemas side. There is an XSList on the XS
side, though I am not sure what these XSxxxx classes are yet, except
wrappers for a JClass. They seem to be a schema type, but then what was
ListType for. In MemberFactory near line 242 or so, there is code to
generate a memberName+"List" that uses this XSList type. The code does
not run down there right now possibly because of a bug. Anyways, if I
fix that code, it does not behave like JAXB spec.
If I am not mistaken, JAXB spec would take this
<xsd:complexType name="Device">
<xsd:attribute name="something" type="List"/>
</xsd:complexType>
<xsd:simpleType name="List">
<xsd:list itemType="xsd:string"/>
</xsd:simpleType>
And generate one method in Device.java called getSomething() that
returns a java.util.List. In the MemberFactory, the code produced using
XSList instead generates addSomething(int index), removeSomething(int
index), enumeration().......Should I redo this so it coincides with the
JAXB spec, or should I just fix the bug so that
addSomething/removeSomething is generated. Am I way off base here?
Maybe that XSList only has something to do with the generations when
extraCollectionMethods=true. Please point me in the right direction here.
thanks,
Dean
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
