Just to report back to this group that this problem has a fix from John
Wilson.

The problem was that my JSP server (Websphere running on zOS) has the
default encoding set to Cp1047 which I didn't know of.  John gave me the
patch to set the encoding to ISO8859_1 manually in MinML.java, which has
worked for me.  It actually fixes my other problem which I reported earlier
in a different thread about the buffer size > 512.  I have attached the
patch code for anyone who might run into the same problem.  

The symptons I was getting were: invalid control character (on client),
header too long (> 512) (on client), garbled text received on the WebServer
console.

The patch is, in MinML.java,  change the parse method to the following:

public void parse(final InputSource source) throws SAXException, IOException
{
  if (source.getCharacterStream() != null)
    parse(source.getCharacterStream());
  else if (source.getByteStream() != null)
    parse(new InputStreamReader(source.getByteStream(), "8859_1"));
 else
    parse(new InputStreamReader(new
URL(source.getSystemId()).openStream()));
}


I am most grateful to John Wilson for his willingness to help me debug my
problem and providing me with a temporary solution.

Thanks.

- Yaxiong




> -----Original Message-----
> From: John Wilson [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, March 08, 2002 10:57 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: Illegal control character error
> 
> 
> ----- Original Message -----
> From: "Lin, Yaxiong" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, March 08, 2002 4:52 PM
> Subject: RE: Illegal control character error
> 
> 
> >
> > John:
> >
> > I am making some progress here.  I changed to use ISO8859_1, and
> > XmlRpcClient (instead of XmlRpcClientLite)  and now the xmlrpc webserver
> is
> > receiving the request from the websphere client no problem.
> >
> > But I am getting the null object returned from the execute command.  I
> have
> > the debug turned on on both client and server, but do not see any error
> or
> > exception.  Any advice on how to debug this problem?
> 
> Excellent!
> 
> Do you use an IDE? Can you run the client under the IDE's debugger? That
> would let you trace the processing of the response. Otherwise I would
> suggest that you put system.out.prinln() calls into the XML-RPC code.
> 
> John Wilson
> The Wilson Partnership
> http://www.wilson.co.uk

Reply via email to