EclipseLink MOXy 2.5.0 snapshot incompatability requiring attribute to be added to proporder

Question

Everything was working fine with my maven enabled project.

But when I rebuilt it today tests started to fail withe error

the property or field count on the class org.musicbrainz.mmd2.DiscList 
is required to be included in the propOrder element of the XmlType annotation

no code had changed so I assume something has changed in the eclipselink MOXy 2.5 snaphot jar.

I could resolve it by removing the offending mapping from oxml.xml

<java-type name="DiscList">
    <java-attributes>
        <xml-element java-attribute="count" name="disc-count"/>
    </java-attributes>
</java-type>

but then my resultant json is incorrect (because I need to rename count to disc-count).

I can fix it my modifying my DiscList.java class and adding to propOrder as suggested by the exception

i.e

from

@XmlType(name = "", propOrder = {
    "disc"    
})

to

@XmlType(name = "", propOrder = {
    "disc","count"
})

but that is a pain because these classes are generated automatically from a schema, I don't want to have to manually edit them every time the schema changes.

So the question really is what has changed in MOXy, and has this change introduced a bug ?

Answer 1

We made this change to EclipseLink MOXy in versions 2.4.2 and 2.5.0 (both streams are currently in development). This change was made to mirror the corresponding behaviour in the JAXB reference implementation.

Related Bug

• http://bugs.eclipse.org/372276

Recommended Fix

If you add a new mapping in the external mapping file (which is a bit rare since you would have had to explicitly remove the mapping via annotations - http://blog.bdoughan.com/2012/04/jaxb-and-unmapped-properties.html). Then you will need to override the propOrder in the external mapping file as well.

<java-type name="DiscList">
    <xml-type prop-order="disc count"/>
    <java-attributes>
        <xml-element java-attribute="count" name="disc-count"/>
    </java-attributes>
</java-type>

Send Us Your Feedback

We like to get feedback on changes we make, especially on streams that are still in development. This best mechanisms for this are:

• EclipseLink Forum: http://www.eclipse.org/forums/index.php?t=thread&frm_id=111
• EclipseLink Users Mailing List: eclipselink-users AT eclipse.org
• Enter a Bug: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EclipseLink

For More Information

• http://blog.bdoughan.com/2010/12/extending-jaxb-representing-annotations.html

---

UPDATE

Thanks for the answer although I'm not convinced requiring me to add element to prop order just because I want to rename it is an improvement. I don't know why count is not already in the proplist I haven't taken it out it just wasn't added when the classes were autocreated with JAXB.

If your Java class was generated from an XML schema and count corresponds to an XML element then it should have been in the prop order. MOXy uses the same XJC code as the reference implementation and the JAXB RI also throws an exception if the propOrder is incomplete so I'm not sure what scenario would have excluded it. Would you mind posting the generated class? I would like to see if there is an actual bug here.

Also it would be useful if the eclipselink maven repository was browsable, the download.eclipse.org/rt/eclipselink/maven.repo page doesn't given any indication of changes made to the snapshot.

We're working on improving our Maven setup. I would recommend entering this as an enhancement request against the build component:

• https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EclipseLink