+1 for me. I think the JAXP/TRaX apis pretty much mirror what exists in Xerces, and have been using it a lot in my code. It is also used in the Cocoon serialization code.
-----Original Message----- From: Kevin Ross [mailto:[EMAIL PROTECTED] Sent: Monday, May 13, 2002 3:59 PM To: [EMAIL PROTECTED] Subject: RE: XML serializing I'm with Stefano, the JAXP/TRaX API is quite easy to use and most Java/XML developers will be familiar with it. -----Original Message----- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] Sent: Monday, May 13, 2002 3:00 PM To: [EMAIL PROTECTED] Subject: Re: XML serializing James Bates wrote: > Been investigating the issue of XML serializing, which seems to happen > in too many different in too many > places in Xindice. Xerces contains a good serialization implementation > in the org.apache.xml.serialize package: > It CORRECTLY handles namespaces, intl character encodings, indenting > when required etc... > > The interfaces are identical in Xerces 1.xxx and Xerces 2.xxx so there > isn't really a risk here either. > > Would you guys accept if I investigated moving Xindice to this more > standard method of serializing, thus doing away > with StringSerializer and TextWriter classes in the Xindice code? > > James > Hmmm, question: what's wrong with using the JAXP 1.1 API for serializing? that comes for free in JDK 1.4 and it's actually implemented by those classes you mention above. -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. <[EMAIL PROTECTED]> Friedrich Nietzsche --------------------------------------------------------------------
