Inconsistent unmarshalling with MOXy?

Issue The inconsistent behaviour is due to properties being overridden in the child class. MOXy considers the properties in both the parent class and child class to be mapped and depending on the order processed you are seeing one behaviour or the other. Solution #1 You need to tell MOXy that the parent properties are not mapped, you can do this by specifying @XmlAccessorType(XmlAccessType.

NONE) on the AggregateRecord and AggregateReport classes: import javax.xml.bind.annotation. XmlAccessorType; import javax.xml.bind.annotation. XmlAccessType; @XmlAccessorType(XmlAccessType.

NONE) public class AggregateRecord { ... } Then specifying @XmlAccessorType(XmlAccessType. PROPERTY) on the SpecificAggregateRecord and SpecificAggregateReport classes: import javax.xml.bind.annotation. XmlAccessorType; import javax.xml.bind.annotation.

XmlAccessType; @XmlAccessorType(XmlAccessType. PROPERTY) public class SpecificAggregateRecord extends AggregateRecord { Solution #2 If you are overriding the accessors on the subclass solely for the purpose of applying a mapping you may want to consider using MOXy's external mapping file instead. Below is an example: http://bdoughan.blogspot.com/2010/12/extending-jaxb-representing-annotations.html Please let me know if you are interested in exploring this option.

I finally got back to this and though I had to specify XmlAccessType. FIELD rather than PROPERTY, it appears to be working consistently now. – Guildencrantz Jul 4 at 23:08.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.