I haven't reviewed it myself in aeons, so I have no opinion beyond "Yup, good question." But I definitely approve of shared code, as long as there aren't irreconcilable conflicts in demands upon it. If both the Xalan and Xerces teams are convinced of that, I'd say go for it.
One architectural question: If it's to be shared, should it no longer be "the Xalan serializer" -- ie, one that lives in the Xalan project -- but instead be moved out to xml-commons? Hopefully unnecessary reminder: The fact that code lives in another Apache project doesn't make maintaining/enhancing it "someone else's problem"; projects with dependencies also accept responsibility to keep those supporting projects healthy. The goal here should be to _share_ effort and responsibility, not transfer it! ______________________________________ "... Three things see no end: A loop with exit code done wrong, A semaphore untested, And the change that comes along. ..." -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
