Community

Hej hej,

in some cases your solution solved my problem. But I still have some cases where the JAXBElement occures in the Java code.

This definition in the WSDL...

<element name="Name" type="tv:NameType"/>
<complexType name="NameType">
     <sequence minOccurs="1" maxOccurs="unbounded">
          <element name="begin" type="xsd:time" minOccurs="1" maxOccurs="1"/>
          <element name="end" type="xsd:time" minOccurs="1" maxOccurs="1"/>
     </sequence>
          <attribute name="begin" type="tv:AnotherType" use="required"/>
          <attribute name="end" type="tv:AnotherType" use="optional"/>
</complexType>

... will be this Java code:

@XmlElementRefs({
     @XmlElementRef(name = "begin", namespace = "http://...", type = JAXBElement.class),
     @XmlElementRef(name = "end", namespace = "http://...", type = JAXBElement.class)
})
     protected List<JAXBElement<XMLGregorianCalendar>> beginAndEnd;
     @XmlAttribute(required = true)
     protected AnotherType begin;
     @XmlAttribute
     protected AnotherType end;

I do not know why there is still this occurence of the JAXBElement and it is not very nice to use in the code. Any suggestions/explanations?

Thanks,

F.