Exactly my point. org.apache.xml.serialize.XMLSerializer,OutputFormat is used ONLY in one file namely XMLCipher.java. We are better off gaining compatability with any JAXP compatible parser. We are forcing people to use a specific xerces version EVEN if they have other parsers in their environment. Hope we have learnt the lessons for the xalan fiasco (we used to fail miserably with the built in xalan in JDK 1.4 and had to use the endorsed over ride mechanism till we fix our code - http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19916)
thanks, dims --- Erwin van der Koogh <[EMAIL PROTECTED]> wrote: > > Surely it's better to say "if you have this bug then download a version of > > Xerces greater than x.x" rather than "fixing" a bug in someone else's code > > with a hack in yours? That's just asking for maintenance headaches isn't > > it? > > Well.. right now we are dependent on Xerces for a single tiny Xerces-only > feature. And if I am not entirely mistaken it might even be the > serialization part. > > So if that's the case and we do go down the custom serializer part we would > be compatible with any JAXP compatible parser, easing maintenance headaches > somewhat. > > So it might actually be easier to maintain in the long run. > > Erwin ===== Davanum Srinivas - http://webservices.apache.org/~dims/
