mmmmm... Well, you know, John, I've just tried io taglib to get a rough output. Actually I just use Xindice XML-RPC, and result is the same. I've just received response from Xindice user list (yep! it works.), Tom Bradford told me, that
"I believe that you can tell Helma/Apache XML-RPC which encoding to use when it serializes its output. Not sure what the API call is though. Setting it to UTF-8 might fix your problem. " And I feel the same... server to use xerces... well, there is a Xindice working as server (if I understand what happens properly), and it use Xerces. ----- Original Message ----- From: "John Wilson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 10, 2002 1:04 AM Subject: Re: xml-rpc & encoding > Philipp Chudinov wrote: > > Yes, Xindice XML-RPC seats ontop of Apache XML-RPC project (well, > > that is org.apache.xmlrpc package). The problem is here: > > > > //posted 2 xindice users (no response, so slow ppl...) > > < > > Well, I've tried jakarta io taglib to create an XML-RPC call to get a > > document from the Xindice. The response looks like follows: > > OK, so the XMl-RPC response is being generated by jakarta io taglib not by > the Apache XNL-RPC server. This explains a lot. > > Can you get it to use ISO-8859-1 encoding? this would mean that it would > send Unicode characters > 255 as &#xxxx; Apache XML-RPC will be happy with > this. > > > Another solution may be to remove the encoding from the XML declaration and > get the server to use Xerces instaead of MinML (you can sert a propaerty or > pass a parameter to do this). > > The current version of MinML doesn't handle the encoding declaration (I'm > fixing that). > > Hope this helps. > > John Wilson > The Wilson Partnership > http://www.wilson.co.uk >
