The issues you're mentioning are indeed very important.
But the thing is when you have an xmlblaster client publishing a message
with eg. the oid = Jack&Moud, you'll get a parse error on the server side,
because the XML that is sent over between client and server is invalid.
As long as the application programmer does not use any 'special' characters,
everything should work fine. But I think it's not a good idea to put
a restriction on the use of 'special' characters.
From: owner-xmlblaster-devel at server.xmlBlaster.org
[mailto:owner-xmlblaster-devel at server.xmlBlaster.org]On Behalf Of Marcel
Sent: vrijdag 6 augustus 2004 9:49
To: xmlblaster-devel at server.xmlBlaster.org
Subject: Re: [xmlblaster-devel] XML generation
Quartier, Nicolas wrote:
> The xml used by XMLBlaster is parsed with a SAX parser it seems.
> But for the generation of XML strings, no parser is used, resulting in
> incorrect XML. (StringBuffers are used to generate the XML strings)
> The result is that special characters like &, at , ... can not be used.
> eg "Jack&Moud" needs to be translated into "Jack&Moud".
> Further information can be found on:
This is a nice overview, our constraints to change
to another xml generation technique are:
- support for JDK 1.2 up to 1.5
- keep performance
> Has anyone else already tried to used some of those special characters ?
> Kind regards,