+1
I'm all for having a common serializer.
I don't think there is a big enough community of committers justify moving
the serialization code inside of Xalan into a separate project. For now I
suggest that it stay as part of the Xalan project.
There already is a 'build serializer.jar' target inside of the Xalan-j
project and this builds a serializer that is rather small in footprint and
independent of the rest of the code in Xalan-j. This should do. We only
have to take some care about any synchronization of release schedules, but
I think that is the lesser evil compared with the effort of splitting it
out.
- Brian
- - - - - - - - - - - - - - - - - - - -
Apache Xalan PMC Member
Neil
Delima/Toronto/IB
[EMAIL PROTECTED]
To
[email protected]
07/11/2006 06:37 cc
PM [email protected]
Subject
Re: Moving towards common
Please respond to serialization code...
[EMAIL PROTECTED]
he.org
Hi All,
It's been over two years since the idea of moving towards common
serialization code was proposed and discussed on the Xerces-J and Xalan-J
dev mailing lists[1]. Xalan's serializer has the same baseline capability
as Xerces' Java serializer, effort was devoted to improve its performance
and fix bugs and it is being maintained by Xalan-J community and so we
should use Xalan's serializer as the primary code base moving forward.
Xerces's the HTML and XHTML serializers have been deprecated since Xerces
2.6.2. We should now deprecate Xerces' XML serializers but would first
need to migrate DOM Level 3 to use Xalan's serializer which Xerces could
pick up and use. I am willing to take on this work. Once this work is
complete, we would be in position to deprecate Xerces's XML serializers
after the next major release.
Xalan's serializer can be packaged as a standalone jar and does not to have
dependencies on other components in Xalan. So it can continue to reside as
a standalone serializer component in Xalan.
In general, to achieve interoperability, users should be using the JAXP 1.3
Transformation API to serialize HTML, XHTML and XML streams, SAX events
(and DOM) and DOM Level 3 to serialize a DOM, which could be based on
common serializer code.
Thoughts?
Thanks,
Neil Delima / IBM Toronto Lab
[1] http://marc.theaimsgroup.com/?l=xalan-dev&m=107593381313807&w=2
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
