> 
> I'm in the process of trying out Apache XML-RPC's behaviour 
> on the strings issue. I'll get back when I have some definite results.
> 
> James
> 


And the answer is: it's no better than CORBA: Java strings containing characters
other than those present in Java's now infamous "default character encoding" 
(aka iso-8859-1 on my system: french, spanish, italian, german, etc...), such 
as Greek or Russian come out the other end as a bunch of question marks. 
Probably the XML-RPC code itself also uses Java's "default" conversion methods 
when converting to InputStreams and OutputStreams: the question marks are a 
typical indication of that. 

This is a definate -1 for XML-RPC in my view... Fixing required either


  * buggering around in XML-RPC source, adding "utf-8" args everywhere, much 
like I did for Xindice

  * leaving XML-RPC as is, but taking care never to directly pass strings to 
it, only encoded byte-arrays we produce ourselves in Xindice.

I'd like to look at really how complicated it would be to go for SOAP straight 
away.

James

Reply via email to