Mailing-List: contact commons-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
In-Reply-To: <42A415E2.9010702@sun.com>
To: commons-dev@xml.apache.org
Cc: Neeraj.Bajaj@Sun.COM
MIME-Version: 1.0
Subject: Re: Remaining work for JAXP 1.3 APIs
Message-ID: 
 <OF7E6BC93D.029D804D-ON85257018.00500D25-85257018.00509794@ca.ibm.com>
From: Michael Glavassevich <mrglavas@ca.ibm.com>
Date: Mon, 6 Jun 2005 10:40:17 -0400
Content-Type: text/plain; charset="US-ASCII"

Neeraj Bajaj <Neeraj.Bajaj@Sun.COM> wrote on 06/06/2005 05:22:42 AM:

> 
> 
> Michael Glavassevich wrote:
> 
> > A 
> >diff [4] between the latest copies on the main branch and 
tck-jaxp-1_2_0 
> >shows some other differences, most notably how the jaxp.properties file 
is 
> >cached. The code on the main branch will read and cache the 
> >jaxp.properties file once whereas on the tck-jaxp-1_2_0 branch it will 
> >reload it if the jaxp.properties file was modified since it was read 
> >(which to me appears to be a more desirable behaviour).
> > 
> >
> Former is the correct behavior. As per the spec. jaxp.properties should 
> be read only once.
> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/parsers/SAXParserFactory.html#newInstance()

Interesting. The previous version of the spec didn't have this statement 
[1] appearently giving implementations the freedom to choose their own 
caching strategy.

[1] 
http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/parsers/SAXParserFactory.html#newInstance()

> - Neeraj
> 

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org