Multiple @XmlElement with the same @XmlElementWrapper

[dmlloyd]

As the subject hints, I'm trying to do this:

    // ...
    public List<SocketAddressMetaData> getBindings() {
        return bindings;
    }

    @XmlElementWrapper(name = "bind")
    @XmlElement(name = "bind-address")
    public void setBindings(final List<SocketAddressMetaData> bindings) {
        this.bindings = bindings;
    }

    public List<ManagedBindingMetaData> getManagedBindings() {
        return managedBindings;
    }

    @XmlElementWrapper(name = "bind")
    @XmlElement(name = "managed-binding")
    public void setManagedBindings(final List<ManagedBindingMetaData> managedBindings) {
        this.managedBindings = managedBindings;
    }
    // ...

It doesn't complain when it reads the annotations, however when it parses I get:

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:xnio:2.1}managed-binding not found as a child of {urn:jboss:xnio:2.1}bind in sequence: {urn:jboss:xnio:2.1}bind-address*
     at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:391)
     at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
     at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
     at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
     at org.apache.xerces.xinclude.XIncludeHandler.emptyElement(Unknown Source)
     at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
     at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
     at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
     ... 44 more

The enclosing type has "propOrder = {}", but I wouldn't think that would apply to the intermediate wrapping type which I'd want to be a "choice" with "maxOccurs = "unbounded"".

Ideas?

[dmlloyd]

Addendum - I haven't been able to find any examples of this particular usage pattern, however @XmlElementWrapper does support nested @XmlElements, so it seems like it should work.

[aloubyansky]

AFAIU your binding is

<xsd:complexType>

   <xsd:all>

      <xsd:element name="bind">

         <!-- skip some type and sequence -->

         <xsd:element name="bind-address" type="..." maxOccurs="unbounded"/>

      </xsd:element>

      <xsd:element name="bind">

         <!-- skip some type and sequence -->

         <xsd:element name="managed-binding" type="..." maxOccurs="unbounded"/>

      </xsd:element>

   </xsd:all>

</xsd:complexType>

[dmlloyd]

Hmm, shouldn't that give an error when building the schema then?  Also, @XmlElementWrapper can contain @XmlElements; why is this construct not equivalent?  (JSR-222 seems to give no hint about this...)

[aloubyansky]

In this case, yes, we could throw an error (i.e. if there are two elements with the same name in model groups all or choice, in sequence it's legal).

It's not equivalent because it means different things:

- XmlElement - translates into an element

- XmlElements - translates into a choice of elements

And, again, in sequences you could have two elements with identical names with different content and they both could appear in xml at the same time.

[dmlloyd]

I see.  Well in this case I just with the old "List<Object>" approach, poor as that is.