Turns out the type-attribute had nothing to do with the @XmlJavaTypeAdapter annotation. It was caused by the fact, that the Map's elements were of a derived type and MOXy correctly marshalled their type to a type-attribute.
Up vote 0 down vote favorite share g+ share fb share tw.
I am using @XmlJavaTypeAdapter to marshal fields of type Map to XML. This results in EclipseLink-MOXy creating an xsi:type=""-attribute on the output xml-element. Upon validation the referenced type can of course not be found.
Is there any way of suppressing the generation of this attribute? PS: An XmlAdapter-tag would be handy :) jaxb eclipselink moxy link|improve this question asked Jan 18 at 15:39quaylar7977 83% accept rate.
Turns out the type-attribute had nothing to do with the @XmlJavaTypeAdapter annotation. It was caused by the fact, that the Map's elements were of a derived type and MOXy correctly marshalled their type to a type-attribute. Using instead of solved the issue.
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.