On Sun, 2007-12-30 at 07:25 -0800, qvall wrote:
> Thanks for clarification. How can i make cxf use base64 encoding to
> confictual strings then? Any method I should particularly read on? Or maybe
> i have to encode it manually?
You have to force the use of a base64 data type. We don't have an
automatic scheme for this that I know of. I'd do it by declaring byte[]
instead of String. Are you using Aegis or JAXB?
If the data is larger than small, I think I should be pushing you to
consider MTOM or some other attachment scheme.
>
>
>
> Benson Margulies-4 wrote:
> >
> > CDATA doesn't help illegal characters. They can't be in XML, at all. Not
> > in
> > CDATA, not in &#. You need use attachments or base64 if you need to send
> > them around.
> >
> > On Dec 29, 2007 6:29 PM, qvall <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> Hi,
> >> Is there any way to translate illegal characters that are in the xml
> >> message?
> >> I'm receiving
> >> javax.xml.ws.soap.SOAPFaultException: Unmarshalling Error:
> >> Illegal character ((CTRL-CHAR, code 7))
> >> and I'm wondering why text nodes are not encompassed with CDATA section?
> >> Do you know any simple workaround without doing it manually?
> >>
> >> And the last simple question. Is there any way to make
> >> LoggingInInterceptor
> >> print formatted output? I mean with proper identation,
> >>
> >> patrick
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Illegal-characters-in-xml-tp14542696p14542696.html
> >> Sent from the cxf-user mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
