Shane Curcuru <[EMAIL PROTECTED]> wrote on 02/12/2006 07:24:55 AM: > I really thought I replied earlier! Yes, I would love to see a new > release of xml-commons-external. However, there are a couple of > questions we need answered. Anyone from the Xerces/Xalan teams want to > chime in with the info, since they've done much of the maintenance in > the past here? > > - What are all the different branches of xml-commons-external code, and > more importantly, what versions of DOM/SAX/JAXP are they each supposed > to support?
There are a bunch but I'd only consider three of them to be active: the main trunk, tck-jaxp-1_2_0 and external-extended. The main trunk contains JAXP 1.3, SAX 2.0.2 and DOM Level 3. This is the API code donated by Sun last year plus several bug fixes and improvements. Both Xerces-J 2.7.1 and Xalan-J 2.7.0 shipped xml-commons-external-1_3_02 which is the most recent tag on the trunk. A few bug fixes and other minor changes have been applied since then. The tck-jaxp-1_2_0 branch contains JAXP 1.2, SAX 2.0.1 and DOM Level 2. Previous versions of Xerces and Xalan which supported JAXP 1.2 got their APIs from this branch. The most recent tag is xml-commons-external-1_2_04. The external-extended branch was just created this month. It contains some additional APIs (SAC 1.3, SMIL and SVG 1.1) which were formerly bundled with Batik. It updates DOM Events to level 3. You can read more about it here [1] and here [2]. None of the other branches have had any activity in the last three years. > - Who here has direct access to the appropriate JAXP 1.3 TCK and can run > it on our code? While it's slightly legally unclear to me if an > xml-commons-external release itself must pass the TCK, we really need to > know if it will pass or not. (Given that xml-commons-external only > includes the interfaces, and doesn't actually include an implementation > of JAXP itself, I haven't studied if it has to independently pass the > TCK, or if only implementers like Xerces/Xalan/etc have to pass the TCK > itself. The JAXP 1.3 TCK is available [3] at the ASF. Any project which needs it can request access. I suppose you could test the pieces individually but to pass the TCK you need to run it with a complete implementation: APIs + Xerces + Xalan. > - Shane [1] http://mail-archives.apache.org/mod_mbox/xml-commons-dev/200506.mbox/[EMAIL PROTECTED] [2] http://mail-archives.apache.org/mod_mbox/xml-commons-dev/200602.mbox/[EMAIL PROTECTED] [3] http://www.apache.org/jcp/ Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
