Mailing-List: contact commons-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 23 Sep 2002 10:24:11 +0200
From: Libor Kramolis <Libor.Kramolis@Sun.COM>
Subject: Re: JAXP 1.2
To: xerces-j-dev@xml.apache.org, commons-dev@xml.apache.org,
        xalan-dev@xml.apache.org
Message-id: <3D8ECFAB.6020307@Sun.COM>
Organization: Sun Microsystems, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827
References: 
 <OF5011A9B3.6B646898-ON85256C36.0056FFC6-85256C36.0058B0D6@us.ibm.com>
Status: O

I am mainly looking for release transparency of versions of bundled 
libraries, i.e. part-of-xml-apis in xerces release; xml-apis and xerces 
in xalan release.

I never saw stable release of xml-commons and it is little bit confusing 
to me, who develop it for and if it is a primary place for JAXP (and 
also other things). I think there could be stable releases of JAXP 1.1 
and JAXP 1.2. Available for everyone, any JAXP implementation (including 
Xerces and Xalan).

Xerces release should bundle stable release of JAXP and there should be 
information which version of JAXP it implements and which version of 
xml-apis it bundles. I do not see any reason xerces should bundle 
own/changed version of xml-apis -- it is not transparent.

Same to Xalan, I think its release should bundle stable release of JAXP 
and Xerces and there should be information which version of JAXP it 
implements and which version of JAXP and Xerces it bundles.

I hope it is possible to upgrade any part (xml-apis, xerces, xalan) by 
new bug-fix release (minor release: x.y.A -> x.y.B) with no problems.

Thanks for understanding.

Regards,
Libor


Joseph Kesselman wrote:
>>What is the relation between released JAXP 1.2 [1] and Apache XML 
> 
> Commons. 
> 
>>What is relation between specification and implementation, i.e. commons 
> 
> vs. xerces and xalan? 
> 
> Commons is intended to contain standards based elsewhere (DOM, SAX, JAXP, 
> etc), possibly plus some shared Apache utilities. 
> 
> Yes, Commons and the implementations should be kept up to date as the 
> standards evolve -- as time permits, which is true of any Apache project. 
> If you want it to happen faster, work to get yourself accepted as a 
> committer and volunteer to help work on that task... but note that these 
> projects _DO_ need to stay in synch in order to compile cleanly against 
> each other.
> 
> The simplest way to ensure that everything is in synch is to take the 
> version of Xerces that your version of Xalan was compiled and tested 
> against; check the Xalan docs for details.
> 
> 
> Xalan compiles directly against Commons, and in fact compiles all of 
> Commons into its xml-stds.jar file. Xerces has been taking a selected 
> subset of Commons as the content of its xmlParserAPIs.jar file. There's 
> been some discussion of whether that subsetting is really a net win, but I 
> don't think a consensus has been reached.
> 
> ______________________________________
> Joe Kesselman  / IBM Research / Xalan, plus some past work on Xerces and 
> Commons
> 

-- 
Libor Kramolis, Software Engineer      | <libor.kramolis@sun.com>
NetBeans/Sun Microsystems, XML Project | http://xml.netbeans.org/