Indeed, the CXF JAXB data binding does not provide any simple way around this.
In the example at hand, the code knows the target byte stream for the output, and is concocting a specialized XML writer that has the desired behavior. CXF uses StaX to write out XML. You'd need a StaX implementation. I wonder if you could create an interceptor that rewrote the XML the way you like it? I'm not much of an interceptor expert. On Sat, Mar 1, 2008 at 4:32 PM, Benson Margulies <[EMAIL PROTECTED]> wrote: > Why do you want to do this? The distinction between CDATA and various > &-entities is way below the level of web service semantics. Any conformant > XML parser is going to treat them identically. > > > On Sat, Mar 1, 2008 at 2:01 PM, Todd Orr <[EMAIL PROTECTED]> wrote: > > > I'm attempting to get String data wrapped in CDATA before being > > returned to the client. I do not want special characters to be > > escaped. First I tried simply wrapping the properties in my getters > > with the CDATA block. Unfortunately, JAXB continued to escape all the > > special characters. > > > > I found this post: > > http://forum.java.sun.com/thread.jspa?threadID=607524&messageID=3531931. > > Although promising, I could not find out how to setup JAXB in my > > applicationContext in such a way to set this as the XMLSerializer. > > > > Has anyone accomplished this? It seems as though it would be a fairly > > common need. > > > > Thanks, > > T > > > >
