Moving towards common serialization code... 2006-07-11 - By Neil Delima
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
<br><tt><font size=2>Hi All,</font></tt>
<br>
<br><tt><font size=2>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.</font></tt>
<br>
<br><tt><font size=2>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. <
/font></tt>
<br>
<br><tt><font size=2>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.
</font></tt>
<br>
<br><tt><font size=2>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.</font></tt>
<br>
<br>
<br><tt><font size=2>Thoughts?</font></tt>
<br>
<br><tt><font size=2>Thanks,<br>
Neil Delima / IBM Toronto Lab<br>
</font></tt>
<br><tt><font size=2>[1] http://marc.theaimsgroup.com/?l=xalan-dev&m
=107593381313807&w=2</font></tt>
<br>
|
|
