This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 40121 - Xerces 2.6.2 upgrade
Summary: Xerces 2.6.2 upgrade
Status: VERIFIED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: libs (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: Milan Kuchtiak
URL: http://xml.apache.org/xerces2-j/relea...
Keywords: ARCH
Depends on:
Blocks:
 
Reported: 2004-02-15 21:55 UTC by Jesse Glick
Modified: 2004-09-06 15:32 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2004-02-15 21:55:39 UTC
Xerces 2.6.1 has apparently been out for a couple
of weeks now and we should strongly consider
bundling it in NB 3.6:

http://xml.apache.org/xerces2-j/releases.html
Comment 1 Jesse Glick 2004-02-15 22:05:37 UTC
Note that Xerces 2.6.1 permits *proper* validation of namespaced
documents using arbitrary schemas listed in an OASIS catalog,
*without* using xsi:schemaLocation, which AFAIK the current XML module
does not support. So this could be important.
Comment 2 Jesse Glick 2004-05-14 14:11:37 UTC
Old libs should be considered an arch defect.
Comment 3 Petr Jiricka 2004-06-23 10:45:00 UTC
Well, it looks like it's expected the XML team will do the upgrade,
right? Are there any tests that could be run to verify that this does
not break anything (layer file parsing, project file parsing,
performance, ...)?

What are all the places where Xerces is used? The major places I found
are:

WebApps + Tomcat plugin
XML module
API support module
Registry module

Xerces is currently not a part of the platform. Will it be in the
future (for the registry)? Thanks.
Comment 4 Jesse Glick 2004-06-23 13:42:55 UTC
"Are there any tests that could be run to verify that this does not
break anything" - just commit validation I think. BTW it is quite
unlikely that something as simple as layer parsing - quite plain SAX
handler - would be broken by a Xerces upgrade. Problem areas are
probably going to be obscure areas of namespace handling;
functionality of XMLUtil (there is a unit test for this); XNI in the
XML module; etc.

No immediate plans to make it part of the platform. It is used by
Registry only because there is a bug with namespace handling in
1.4.2's Xalans serializer, it seems; fixed in 1.5.0 AFAIK.
Comment 5 Petr Jiricka 2004-07-08 17:20:49 UTC
> Note that Xerces 2.6.1 permits *proper* validation of namespaced
> documents using arbitrary schemas listed in an OASIS catalog,

Does this refer to the following item in the Xerces 2.6.1 release notes?

"Added support for XML Catalogs."

See the release notes at http://xml.apache.org/xerces2-j/releases.html.

Xerces 2.6.1 bundles the entity resolver library, so this is related
to issue 27930.
Comment 6 Petr Jiricka 2004-08-13 14:54:52 UTC
Hey, now I see that this is marked as a P2 defect. It's not tracked in
NB 4.0 quality dashboards though. Do we really want to fix P2s against
the libs module for NB 4.0? If we do, then this should be included in
the dashboards. 
Comment 7 Jesse Glick 2004-08-13 18:07:18 UTC
IMHO yes, this is part of the IDE we ship. If we ship an old version
of a library with bugs in it, we are responsible for problems that may
cause to downstream modules.
Comment 8 Milan Kuchtiak 2004-08-17 11:00:42 UTC
Xerces was updated to 2.6.2
Comment 9 dmladek 2004-09-06 15:32:42 UTC
In  Product Version       = NetBeans IDE Dev (Build 200409051800)

Turning on modules:
        org.openide/1 [4.45 200409051800]
        javax.jmi.reflect/1 [1.1 200409051800]
        org.netbeans.libs.xerces/1 [1.4 2.6.2]
...
...
...