> Question 1:
I see your point.
> This is where I have a large conceptual problem with such a signature.
> However, I'm not sure if this signature is done this way because of the
> reference implementation or if its a requirement from the 0.90 version
> of the spec. I've read most of the spec, but I can't remember, so
> please inform me either way.
I'm reasonably sure that this is what the spec says. IOW, I don't think this
is a bug of RI.
One thing that the end user can do to avoid this it to use a property
customization to change the property name.
<xsd:element name="bathtubToys">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="rubberDucky" minOccurs="1" maxOccurs="unbounded">
<xsd:annotation><xsd:appinfo>
<jaxb:property name="RubberDuckies"/>
</xsd:appinfo></xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
> Question 2:
>
> Why don't JAXB classes implement the java.util.TreeModel interface and
> supporting constructs.
I suppose it's just because nobody just haven't thought about it. I
couldn't find the TreeModel interface in the java.util package.
And I'll let the spec team know about your comments.
regards,
--
Kohsuke KAWAGUCHI 408-276-7063 (x17063)
Sun Microsystems kohsuke.kawaguchi_at_sun.com