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.
The Xerces.jar that Forte 3.0 includes is outdated and does not correctly implement the SAX2 LocalName parameter in the startElement, endElement, startDocument, and endDocument methods of a parser. Please replace it in the final release version with an updated version of the Xerces.jar file ( version 1.4 and above preferable). *** [FFJ CUSTBUG] this bug was reported by customer ***
Hmm. I am not sure we can change it. Forte3.0 is based upon NetBeans 3.2 and there is this version of xerces. More over I am not sure who can make such decision, does anyone know it? BTW, when the user urgently needs to have newest version, he can download it. Do others think the same?
This user knows about replacing xerces.jar and has already done so. I filed this bug as other Forte users may come across this issue in the future.
Documented. It will be replaced in NetBeans 3.3 release.
QA rejected the update in 3.3 release. For 3.4 we can move to Xerces 1.4.4 or we can wait for Xerces 2.0.0.
Provided that nbextra/core/release/lib/ext contains: dom.jar DOM API level 2 sax.jar SAX 2 API jaxp.jar JAXP/parsers API xerces.jar Xerces 2.0.0 implementation (we will need legal approval) following patch migrates standard distribution into Xerces 2.0.0 parser. Ant module is problematic as Xerces2 is not fully back compatible with Xerces1 (the incompatability covers only parser specifics APIs).
Created attachment 4527 [details] Upgrate patch
Also note that the patch forces all modules to declare cleanly compile time dependencies (SAX, DOM or JAXP). Adding QA to CC. It is simple change with complex consequences and need to be well tested.
Comments on patch: 1. Ant module can temporarily ship with its own Xerces 1 parser. Or maybe it can be easily changes to use Xerces 2, I don't know offhand. Also apisupport has the same dependency as Ant - both use it to implement XML two-way editing. 2. It is getting ugly to specify the location of the XML API JAR file in every build script. Please just define it as a <property name="..." location="..."/> once in nbbuild/build.xml and use it in others. (We probably need some way to share property settings for all build scripts when you run them straight out of the module dir... I have an idea here.)
Created attachment 4589 [details] nbbuild bootstrap patch.
Assigning to new core XML maintainer to speed up the resolution (it requires a lot of time to handle legal and possible compatability issues).
Xerces 2.0.1 integrated. I have not done sax.jar, dom.jar, jaxp.jar separation because we still do not have particular legal approval for JAXP binaries.
What's going on with #20269? Does the Ant module's parse/regen support still work?
Xerces 2.0.1 has improved backward compatability, 20269 bug is not exposed by this upgrade.
verified