Hi Neil, I took part in the assessment of the two code bases back in 2004 and fully agree that moving to a shared serializer is the way to go. Thanks for volunteering to work on the DOM L3 migration.
+1. Neil Delima/Toronto/[EMAIL PROTECTED] wrote on 07/11/2006 06:37:53 PM: > > 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 Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
