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? Thanks. - Yaxiong > -----Original Message----- > From: John Wilson [SMTP:[EMAIL PROTECTED]] > Sent: Friday, March 08, 2002 9:55 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 3:06 PM > Subject: RE: Illegal control character error > > > > > > John: > > > > I am still trying to debug this problem, but I want to share with you > what > I > > have found on the newsgroup about the usage of getOutputStream and > > getPrintWriter. The guy reported that on IBM webSphere, getOutputStream > > would return different output object depends on how the servlet is > called. > > If it's called directly from the browser, it would return > > sun.servlet.http.HttpOutputStream, and if called from a JSP inside > > websphere, it would return > com.ibm.servlet.PageCompilePCServletOutputStream. > > On the later case, the char would not be encoded correctly. He also > > reported that the output object returned from getPrintWriter always > encode > > the char correctly. > > > > So, with this information, I was wondering if getPrintWriter should be > used > > to obtain the i/o object to make the code more robustic? > > That's very interesting - it would be worth trying this. If the wrong > encoding mechanism is used then it would certainly explain the error you > are > seeing. > > > John Wilson > The Wilson Partnership > http://www.wilson.co.uk
