It is in Xalan. Their serializer started as a copy of the Xerces one
(even has similar package names: org.apache.xml.serialize vs.
org.apache.xml.serializer). We didn't want to duplicate the effort
anymore and decided to combine forces and the Xalan one was chosen as
the common codebase because it was better maintained and was making
significant improvements to performance. Its LSSerializer
implementation was written by a Xerces committer and I have made
improvements and fixes to it too where I've found issues, so it's
being jointly maintained, though in a different project. This is the
alternative. It *is* an LSSerializer and there is no reason that it
can't be updated / fixed to have similar behaviour, but that's only
likely to happen if users report the problems they're having (patches
are welcome), preferably in JIRA.
If only that were true. I raised a bug (which included a patch) over
two years ago due to different behaviour between the Xerces/Xalan
LSSerializer but it has seemingly been ignored.
https://issues.apache.org/jira/browse/XALANJ-2409
I wonder if LSSerializer bugs are falling between the cracks?
Chris Simmons.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
