This is a known MOXy issue that has been fixed in the EclipseLink 2.3.0 stream. An EclipseLink 2.3.0 download can be obtained here.
This is a known MOXy issue that has been fixed in the EclipseLink 2.3.0 stream. An EclipseLink 2.3.0 download can be obtained here: eclipse.org/eclipselink/downloads/nightl... The workaround for EclipseLink 2.1.2 is to use another access type, or to annotate the corresponding field with @XmlTransient: import javax.xml.bind.annotation. XmlAccessType; import javax.xml.bind.annotation.
XmlAccessorType; import javax.xml.bind.annotation. XmlElement; import javax.xml.bind.annotation. XmlRootElement; import javax.xml.bind.annotation.
XmlTransient; @XmlAccessorType(XmlAccessType. NONE) @XmlRootElement(name="root") public class TestBean { @XmlTransient private String name = null; @XmlElement(name="lastname") public String getName() { return name; } public void setName(String name) { this. Name = name; } }.
OK, yesterday I applied a workaround by using XmlAccessType. FIELD and it worked as expected. – basZero Jan 28 at 7:42 is there an RSS feed I can subscribe to in order to know when 2.3.0 gets final?
Nightly builds are not a candidate for productive systems. – basZero Jan 28 at 7:55.
I tried your test and it gives the correct output for me: abc It could be the JAXB2 implementation (moxy in your case vs native JDK1.6 based JAXB2 for my test).
Yes this is a known MOXy bug, see: stackoverflow. Com/questions/4817275/… – Blaise Doughan Jan 27 at 14:29 Thanks for testing, it is obviously a MOXy issue – basZero Jan 28 at 7:55.
I tried your test and it gives the correct output for me.
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.