Description Rick Barkhouse 2010-04-01 16:45:28 EDT

Consider the following schema:

...
    <xs:complexType name="person">
        <xs:sequence>
            <xs:element name="company" type="xs:IDREF"/>
        </xs:sequence>
    </xs:complexType>

    <xs:complexType name="company">
        <xs:sequence>
            <xs:element name="name" type="xs:string"/>
        </xs:sequence>
        <xs:attribute name="id" type="xs:ID"/>
    </xs:complexType>
...

The JAXB RI will generate the following Java code:

public class Person {
    @XmlElement(required = true)
    @XmlIDREF
    @XmlSchemaType(name = "IDREF")
    protected Object company;
    ...
}

public class Company {
    @XmlAttribute(namespace = "myNamespace")
    @XmlJavaTypeAdapter(CollapsedStringAdapter.class)
    @XmlID
    @XmlSchemaType(name = "ID")
    protected String id;
    ...
}

Because there is no way to tell what Java type 'company' is, it is typed as Object on the Person class.  Since there is no TypeInfo created for Object, we will never generate an XMLObjectReferenceMapping in MappingsGenerator, but instead an XMLCompositeObjectMapping is created instead:

MappingsGenerator line 431:

TypeInfo reference = typeInfo.get(referenceClass.getQualifiedName());
if (reference != null) {
    if (property.isXmlIdRef()) {
        generateXMLObjectReferenceMapping(property, descriptor, namespaceInfo, referenceClass);
    } else {
        if (reference.isEnumerationType()) {
            generateDirectEnumerationMapping(property, descriptor, namespaceInfo, (EnumTypeInfo) reference);
        } else {
            generateCompositeObjectMapping(property, descriptor, namespaceInfo, referenceClass.getQualifiedName());
        }
    }

We will need to be able to support XMLObjectReferenceMappings that do not have a reference class set.