ws-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "remigijus" <>
Subject Re: setEncoding broken? (Was re: accented characters in XMLRPC arguments)
Date Thu, 11 Dec 2003 20:05:43 GMT
For same problem related with encoding I did some changes in the source.
But I still had no sucess for the client part whitch was used from the
I wish you sucess and will be watching what you will come with.

----- Original Message -----
From: "Dylan McNamee" <>
To: <>
Sent: Thursday, December 11, 2003 9:12 PM
Subject: setEncoding broken? (Was re: accented characters in XMLRPC

> At the risk of chatting with myself on a public mailing list, I hereby
> revise my last email to say "it would seem that
> XmlRpc.setEncoding("UTF-8") is broken in 1.2-b1".
> I've tried calling this, as well as "UTF8" (since that's what Java
> seems to like to call it), and regardless, it doesn't seem to affect
> how the parser is configured, nor does whether I call setEncoding
> before or after creating my xmlrpcClient. Regardless of any of these
> permutations, I always get this exception:
> Invalid character data corresponding to XML entity
> &#8730;
> at org.apache.xmlrpc.XmlRpcClient$Worker.execute(
> at org.apache.xmlrpc.XmlRpcClient.execute(
> ...
> In this discussion:
> The author of MinML says he's working on encoding-related stuff, but
> that was in March, and nothing seems to have moved.
> Does anyone else see this?
> Thanks!
> dylan mcnamee

View raw message