JAXB 2.x with MOXy (Eclipselink 2.1.2): persisting XHTML as element value?

Update and solution regarding MOXy version 2.3.0: I have tried out version 2.3.0 of EclipseLink now and it works!

Update and solution regarding MOXy version 2.3.0: I have tried out version 2.3.0 of EclipseLink now and it works! Here is my data object that I persist: import org.eclipse.persistence.oxm.annotations. XmlCDATA; @XmlAccessorType(XmlAccessType.

FIELD) @XmlRootElement(name=DialogMessage. ROOTNAME, namespace="...") public class DialogMessage { @XmlTransient public static final String ROOTNAME = "dialog"; @XmlElement(name="content-html", namespace="...") @XmlCDATA private String contentHTML = null; public String getContentHTML() { return contentHTML; } public void setContentHTML(String contentHTML) { this. ContentHTML = contentHTML; } } and the MOXy enabling config files: package-info.

Java: @javax.xml.bind.annotation. XmlSchema( namespace = "...", xmlns = {@javax.xml.bind.annotation. XmlNs(prefix = "z", namespaceURI ="...")}, elementFormDefault = javax.xml.bind.annotation.XmlNsForm.

QUALIFIED) package com.yourdomain. Packagenametodataclass; and the jaxb. Properties: javax.xml.bind.context.

Factory=org.eclipse.persistence.jaxb. JAXBContextFactory When I write an instance of DialogMessage as XML to disk, the XML looks like this: sgd asdf asdf asdf> Please note that "..." is just a replacement for whatever namespace URI you have.

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.