xml-rpc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Megacz <a...@megacz.com>
Subject Re: org.apache.xmlrpc.XmlWriter emits invalid XML
Date Mon, 19 Aug 2002 22:27:37 GMT

> > These characters are not allowed even if they are encoded as &#XXXX;
> > The only correct behaviour is to refuse to handle data containing these
> > characters.

> So rather than entity encoding the characters, an XmlRpcException of
> some sort should be thrown?

Ah, the joys of the self-contradictory XML-RPC spec ;) 

  "<string> [is an] ASCII string"

  "Any characters are allowed in a string except < and &... A string can
   be used to encode binary data."

Dave absolutely refuses to fix or clarify this.

Personally, I would advocate John's approach, combined with support
for the <unicode> element from the XMC draft:


If the other end can't understand <unicode>, it will fault. Non-ASCII
characters aren't allowed under XML-RPC, so a fault is the desired
behavior -- there is no way to send non-ASCII characters within the
bounds of the spec without using the <unicode> element.

I can write up a patch for this if you like.

  - a

Sick of HTML user interfaces?

View raw message