JAXP / Crimson update

[Stephane Bailliez <sb...@apache.org>]

As a newbie committer and before someone -1 my changes and send me to hell
[ I'm walking on eggs with CVS :-(  ]

I would like to suggest to update to crimson 1.1.1 which is a bug-fix
release.It should not hurt to ship Ant 1.4 with a updated parser that most
people are not aware it exists especially since it is not even mentioned on
the
crimson web page and you have to go to the download sections to figure there
is a bug fix release available. Among things, it fixes the dreaded bug that
prevents in the JAXP release to do a Document::importNode(Document).

This bug fix release (or part of it) is the one shipped in JDK 1.4beta and
J2EE1.3beta
It is available here: http://xml.apache.org/dist/crimson/

Additionaly...

There is a new jaxp.jar binary in the bug release...There is no information
available for a new version where it should be (ie http://java.sun.com/xml).
Looking deeper in the jar and in the JDK 1.4beta sources, it looks like one
fundamental difference from JAXP 1.1 is the way it loads the factory. There
is now a FactoryFinder class (static inner class of SAXParserFactory) that
is used to get factories via the context classloader first (I guess this is
also what Costin mentioned last time) instead of the previous
Class.forName(String) use.

There are some differences between the code in the jaxp.jar in the bugfix
release and the one in the JDK 1.4, but it looks like similar in the
strategy.

What's your opinion ?

+1 for me. :)

Stephane

Re: JAXP / Crimson update

[Stefan Bodewig <bo...@apache.org>]

On Sat, 28 Jul 2001, Stephane Bailliez <sb...@apache.org> wrote:

> I would like to suggest to update to crimson 1.1.1 which is a
> bug-fix release.

+1

> There is a new jaxp.jar binary in the bug release...

I'm not sure, whether we could legally distribute this jaxp.jar - as
long as it is not available as part of a JAXP 1.1.1 release or
similar.

Is there any license statement that applies to this?  The JAXP 1.1
license will not apply to a modified version and we are probably not
allowed to distribute parts of beta releases ...

Stefan

Re: JAXP / Crimson update

[Conor MacNeill <co...@cognet.com.au>]

----- Original Message -----
From: <cm...@yahoo.com>
To: <an...@jakarta.apache.org>
Sent: Sunday, July 29, 2001 1:53 AM
Subject: Re: JAXP / Crimson update


> Hi Stephane,
>
> +1
>
> In any case, please wait few days ( maybe a week ) before doing the
> update, the code will be very stable after that.
>
>

Does this mean that there will; be a further release after the 1.1.1 that
is already in the download section?

Can you let us know when it is ready to go? Hopefully before I build the
first beta.

Conor

Re: JAXP / Crimson update

[Stephane Bailliez <sb...@apache.org>]

Hi Costin,

[...]
> In any case, please wait few days ( maybe a week ) before doing the
> update, the code will be very stable after that.

Are you in the 'crimson/jaxp' loop or should we bug Edwin so that we can be
aware of this status ?

Stephane

Re: JAXP / Crimson update

[cm...@yahoo.com]

Hi Stephane,

+1

In any case, please wait few days ( maybe a week ) before doing the
update, the code will be very stable after that.


Costin

> I would like to suggest to update to crimson 1.1.1 which is a bug-fix
> release.It should not hurt to ship Ant 1.4 with a updated parser that most
> people are not aware it exists especially since it is not even mentioned on
> the
> crimson web page and you have to go to the download sections to figure there
> is a bug fix release available. Among things, it fixes the dreaded bug that
> prevents in the JAXP release to do a Document::importNode(Document).
>
> This bug fix release (or part of it) is the one shipped in JDK 1.4beta and
> J2EE1.3beta
> It is available here: http://xml.apache.org/dist/crimson/
>
> Additionaly...
>
> There is a new jaxp.jar binary in the bug release...There is no information
> available for a new version where it should be (ie http://java.sun.com/xml).
> Looking deeper in the jar and in the JDK 1.4beta sources, it looks like one
> fundamental difference from JAXP 1.1 is the way it loads the factory. There
> is now a FactoryFinder class (static inner class of SAXParserFactory) that
> is used to get factories via the context classloader first (I guess this is
> also what Costin mentioned last time) instead of the previous
> Class.forName(String) use.
>
> There are some differences between the code in the jaxp.jar in the bugfix
> release and the one in the JDK 1.4, but it looks like similar in the
> strategy.
>
> What's your opinion ?
>
> +1 for me. :)
>
> Stephane
>