As an aside - we have been having some issues in xml-security around serialisation prior to encrypting a sub-set of a document.
Having a single serialiser in xml-commons would be useful for us as well.
(Xposting to security-dev for information.)
Cheers,
BerinJoseph Kesselman wrote:
I definitely like the idea of sharing our serializers, and moving them to xml-commons so they're generally available to Apache-based XML applications, but I'd like to pause for a sanity-check.
1) There have been some known issues in the Xalan "default identity transformation" code -- see the long-standing Bugzilla entry at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5779 That really should be fixed and verified before I would be comfortable with recommending that Xerces cut over.
2) If we're suggesting using the Xalan serializers to write out the contents of a DOM, we should review Xalan's namespace fixups to make sure they're compatable with the recommendations being made by DOM Level 3.
______________________________________ Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more. "The world changed profoundly and unpredictably the day Tim Berners Lee got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
