|
Re: EclipseLink/Moxy 2.4 - some objects not marshalled after correct unmarshalling of XML [message #895040 is a reply to message #894802] |
Wed, 11 July 2012 13:43 |
|
Hi Markus,
This appears to be a bug. You can use the following link to track our progress on this issue:
- http://bugs.eclipse.org/384834
Workaround
package de.dotquality.examples.jaxb.moxy.inheritance;
import java.util.List;
import javax.xml.bind.annotation.XmlElement;
import javax.xml.bind.annotation.XmlElements;
import javax.xml.bind.annotation.XmlSeeAlso;
import org.eclipse.persistence.oxm.annotations.XmlClassExtractor;
@XmlClassExtractor(ContainerClassExtractor.class)
@XmlSeeAlso({Container1.class, Container2.class})
public class Container extends Component {
@XmlElements ({
@XmlElement(name="C", type=Control.class),
@XmlElement(name="C", type=ControlA.class),
@XmlElement(name="C", type=ControlB.class),
@XmlElement(name="CO", type=Container.class),
@XmlElement(name="CO", type=Container1.class),
@XmlElement(name="CO", type=Container2.class)
})
List<Component> subChildren;
}
-Blaise
|
|
|
|
Re: EclipseLink/Moxy 2.4 - some objects not marshalled after correct unmarshalling of XML [message #895347 is a reply to message #895044] |
Thu, 12 July 2012 14:16 |
Markus Rechtien Messages: 4 Registered: July 2012 |
Junior Member |
|
|
Blaise,
I've found a strange problem related to the JDK version and the workaround (no idea if this is a general problem).
When using the annotated classes with either jdk 1.6.0_14 or 1.6.0_32 the binding completely breaks in .._14 and works as expected starting with some jdk version greater .._14.
I haven't figured out yet which version the code starts to work, but when I run my code with the earlier version the implementations are not working as expected.
The reason behind seems that calling Record.get("whatever") in org.eclipse.persistence.descriptors.ClassExtractor.extractClassFromRow(Record, Session)
just returns null instead of the attributes value?! :-/
Is this a known problem?
Best regards,
Markus
Update: I broke it down to somewhere between jdk1.6.0_16 and jdk1.6.0_24 - where it starts to work again...
[Updated on: Thu, 12 July 2012 15:05] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03514 seconds