OK, I really need to go back and read this thread. >From my perspective, there is definite value in having a project to supply just interfaces. But everyone has their own opinion. And we hoped that the first major customers of xml-commons wouldn't be end users, but would be the other Apache xml projects themselves - like how Xalan simply periodically imports the latest xml-commons release, instead of having to manage their DOM/SAX/JAXP code themselves. The point here was to try to get xml projects to have better coordination (which is admittedly going very slowly).
Another question is ease of use: if you buy into xml-apis.jar, you only have one jar for all your interfaces. Other solutions would require users to download and manage separate dom, sax, and jaxp jars, possibly from different sources. While this may sound easy, we've found plenty of real-life users who find this many jars very annoying and who often don't bother to get the right versions. (I hope to find more time for this thread soon but my office is moving next week, so...) ===== - Shane <eof aka="mailto:[EMAIL PROTECTED]"; .sig="Du sublime au ridicule il n'y a qu'un pas." /> __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
