Description Rick Barkhouse 2010-12-16 10:51:34 EST

The JAXB standard way to marshal a byte[] to a hexBinary representation is to use javax.xml.bind.annotation.adapters.HexBinaryAdapter as a Java type adapter.  In annotations this looks like:

@XmlRootElement
public class Customer {
   @XmlElement
   @XmlSchemaType(name="hexBinary")
   @XmlJavaTypeAdapter(HexBinaryAdapter.class)
   public byte[] hexBytes;
   @XmlElement
   public byte[] base64Bytes;
}

This works fine in EclipseLink, but using the equivalent OXM does not:

...
<java-type name="CustomerB">
   <xml-root-element name="customer"/>
   <java-attributes>
      <xml-element java-attribute="picture" xml-inline-binary-data="true">
         <xml-schema-type name="hexBinary"/>
         <xml-java-type-adapter value="javax.xml.bind.annotation.adapters.HexBinaryAdapter"/>
      </xml-element>
      <xml-element java-attribute="resume"/>
   </java-attributes>
</java-type>
...

When marshalled, the <hexBinary> element contains empty string.

This seems to stem from the fact that we go through a different code path if our adapter is not an instance of org.eclipse.persistence.oxm.mappings.converters.XMLConverter.