Hi,
I'm currently trying to complete the basic events part of the Xerces
STaX implementation; one of the things that all the event objects need
to be able to do is serialise themselves as a unicode string compliant
with the relevant productions from the XML spec. Naturally this will
involve doing a certain amount of escaping etc; while this isn't
particularly hard, it seems like the kind of code that ought to exist in
one place and be reused. Currently the obvious place that this code
exists in Xerces is in the serialiser, and it doesn't really look like
it's designed to be reused outside of there at the moment. I was
thinking that it might make sense to factor some of the escaping out
into a utility class somewhere, but IIRC there are plans afoot to move
to common serialisation code anyway... Does anyone have any
suggestions/opinions about the best course of action here? Are there
some other escaping routines I should be looking at instead?
Thanks,
Lucian
--
Lucian Holland, Client Projects Manager +44-1865-203192
DecisionSoft Limited http://www.decisionsoft.com
XML Development and Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
