John:
I am getting this error on the client side (running on webSphere/zOS). I
have the identical client java code running on NT and Solaris (both Tomcat)
talking to the same xmlrpc webserver app and they are all happy.
So, I am pretty sure this control char is not in the data I am sending
through xmlrpc. Any suggestion on how to debug this problem?
Thanks in advance for the advice.
- Yaxiong
> -----Original Message-----
> From: John Wilson [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, March 07, 2002 4:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Illegal control character error
>
> The XML specification does not allow control characters other than /t, /r
> and /n in a document. MinML checks for this and rejects the message. I
> would
> expect Xerces to do the same. If you have to send control characters the
> only option open to you is to send them as a byte array. This will get
> Base64 encoded and the parser will not object.
>
> John Wilson
> The Wilson Partnership
> http://www.wilson.co.uk
> ----- Original Message -----
> From: "Lin, Yaxiong" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, March 07, 2002 9:58 PM
> Subject: Illegal control character error
>
>
> >
> > I am getting "Fatal error parsing XML: Document contains illegal control
> > character with value 20" error. Does anyone know when this character is
> > meant to be? I looked at the MinML class and found this error triggered
> on
> > the charClass retrieval from the string array. Is there anyway to get
> > around this problem?
> >
> > If not, can I use xerces.jar that comes with Tomcat as my parser driver
> and
> > what's the class name I need to use with XmlRpc.setDriver () method?
> >
> > Thanks.
> >
> > - Yaxiong
> >
