On Thu, 26 Jul 2001 00:38, Berin Loritsch wrote:
> Peter Donald wrote:
> > On Wed, 25 Jul 2001 23:17, Stephen McConnell wrote:
> > > Have just completed a build of Avalon and Phoenix over JDK1.4 beta.
> > > Everything's fine except for the DefaultConfigurationBuilder source -
> > > the CVS version contains commented out code that's consistent with the
> > > XML parser libraries including in the 1.4 runtime. Now that I've
> > > updated the source to be consitent with 1.4, my source is now
> > > inconsistent with the CVS and I was wondering if something is planned
> > > concerning any synchronisation in this area?
> >
> > I actually run a patched version locally to use JAXP ... the reason it is
> > commented out is just for backwards compatibility. Also partially because
> > JAXP was broken in some installations (would load only from same
> > classloader jaxp is in rather than context classloader).
>
> The way around that is to keep the JAXP out of the base classloader, and
> add the parser you want when you need it.
Not always an option depending on where you are running it ;(. Some servlet
engines (tomcat3.x at one time) forced it into classpath.
> I think the current version is the best alternative. We can add back in
> the constructor with the classname if you want.
+1
We could even do something like, try jaxp first and if that fails then revert
to old method (or vice versa).
> Who uses anything besides the default constructor?
I know people who set the system property... but used default constructor
still.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
