|
From: | Chris Burdess |
Subject: | Re: End of the month - where is the new snapshot? |
Date: | Wed, 1 Sep 2004 09:18:04 +0100 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Casey Marshall wrote:
About that last point. What do people think about dropping GNU JAXP as external library and let runtime, compiler, tool integrators depend on the GNU JAXP upstream release? Kaffe already does that and I think GNU JAXP is independent enough to point people at it as external extension library.Archie> I agree.. Classpath should avoid trying to duplicate work that Archie> can easily be obtained (freely, of course :-) elsewhere.. Can't we instead just import javax.xml, org.w3c.dom, and org.xml.sax into classpath, and let JAXP work on the concrete implementations of that abstract API?
Ideally this would be logical. However, the XML APIs are prone to backwards-incompatible (ABI) changes, and this means the interfaces and the implementations are much more tightly coupled.
Additionally, once the current release of GNU JAXP is complete, I'd like to move towards JAXP 1.3, which has even more major changes. So I don't think this is quite the right time to do it. - -- Chris Burdess
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFBNYW96dl1DEqHgrgRAkedAJ4hYO4h28IvxcF5XNIj/xJbpW/CGwCeMfgl QKN92tdZVUHDxFtuOlURGow= =/feP -----END PGP SIGNATURE-----
[Prev in Thread] | Current Thread | [Next in Thread] |