You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by Arnaud Le Hors <le...@us.ibm.com> on 2000/12/12 18:40:07 UTC

JAXP 1.1 (was Re: [ANNOUNCEMENT] Xerces-J 2.0.0 (alpha) released. the first release of Xerces 2 initiative)

It turns out that we already got a patch from Costin, that Edwin applied
on November 16, to get Xerces up to date with regard to JAXP 1.1. So
what is missing?
I'm confused.
-- 
Arnaud  Le Hors - IBM Cupertino, XML Technology Group

Re: JAXP 1.1 (was Re: [ANNOUNCEMENT] Xerces-J 2.0.0 (alpha) released. the

Posted by Edwin Goei <Ed...@eng.sun.com>.
Bob Jamison wrote:
> 
> Arnaud Le Hors wrote:
> 
> > It turns out that we already got a patch from Costin, that Edwin applied
> > on November 16, to get Xerces up to date with regard to JAXP 1.1. So
> > what is missing?
> > I'm confused.
> 
> Maybe just the Javadoc was not updated yet? It still says 1.0.

Possibly, I remember applying the patches that Costin gave me.  I think
the code is correct, but the docs need to be updated.

-Edwin

Re: JAXP 1.1 (was Re: [ANNOUNCEMENT] Xerces-J 2.0.0 (alpha) released. the

Posted by Bob Jamison <rj...@lincom-asg.com>.
Arnaud Le Hors wrote:

> It turns out that we already got a patch from Costin, that Edwin applied
> on November 16, to get Xerces up to date with regard to JAXP 1.1. So
> what is missing?
> I'm confused.

Maybe just the Javadoc was not updated yet? It still says 1.0.



Bob



Re: JAXP 1.1 (was Re: [ANNOUNCEMENT] Xerces-J 2.0.0 (alpha) released. the first release of Xerces 2 initiative)

Posted by Edwin Goei <Ed...@eng.sun.com>.
Arnaud Le Hors wrote:
> 
> It turns out that we already got a patch from Costin, that Edwin applied
> on November 16, to get Xerces up to date with regard to JAXP 1.1. So
> what is missing?
> I'm confused.

I don't remember what was updated (neither does Costin) and I can't seem
to find the cvs notification.  In any case, I think only part of the
JAXP changes got implemented, in particular the pluggability part. 
There are other parts of the API that did not get implemented.

-Edwin