Thank you very much Dan, I'm not an AOP expert but I will try to do it and let you know.
Ciao, V. On 10/3/07, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > > it's definitely not something that falls into the "simple to implement" > ball park. > > One option that comes to mind is to write an interceptor that sits > immediately AFTER the StaxOutInterceptor and wrappers the > XmlStreamWriter with a new XmlStreamWriter that forwards the > writeCharacters calls to writeCDATA instead. That would make all the > strings CDATA sections. You could probably analyze the string a bit > first. That probably wouldn't be too hard to do. > > Dan > > > On Wednesday 03 October 2007, Vincenzo Vitale wrote: > > No one with the same requirement? :-( > > > > I know that with normal XML parsers having a CDATA section or an > > escaped one should not be a problem but in my case maybe the third > > party are soing to use a custom old style parser... I'm thing about > > creating a servlet filter to substitute the output in the rest case > > but it seems to me really really old style! > > > > > > Ciao, > > V. > > > > On 9/28/07, Vincenzo Vitale <[EMAIL PROTECTED]> wrote: > > > Hi All, > > > > > > I'm exposing a rest services (using annotation) and the return value > > > is a string with html code inside. The result value is escaped but I > > > would like to have it between <![CDATA[, like it's done with the > > > equivalent Soap service. > > > > > > Is it possible? > > > > > > > > > Thanks, > > > Vincenzo. > > > > -- > J. Daniel Kulp > Principal Engineer > IONA > P: 781-902-8727 C: 508-380-7194 > [EMAIL PROTECTED] > http://www.dankulp.com/blog >
