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.
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
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.
Old libs should be considered an arch defect.
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.
"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.
> 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.
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.
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.
Xerces was updated to 2.6.2
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] ... ... ...