Given the recent comments about how problems with XSL processing were
Sun's fault, I thought it appropriate to forward this.
Peter
-------- Original Message --------
Subject: [Issue 66563] XMLUtil.write produces incorrect namespaces when
using Xalan on JDK 1.5
Date: 1 Jun 2006 22:03:52 -0000
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
http://www.netbeans.org/issues/show_bug.cgi?id=66563
------- Additional comments from [EMAIL PROTECTED] Thu Jun 1 22:03:49
+0000 2006 -------
brianminchau: the NetBeans product doesn't bundle Xalan at all. We use the
version shipped with the JDK, which as far as I know doesn't have this
problem
in the Sun distribution. (Perhaps due to usage of XSLTC?) The problem
arose with
people bundling their own versions of Xalan with add-on modules, in
which case
the rest of the IDE would pick up the bundled Xalan instead of using the
JDK's
version. There is already a workaround in NetBeans which deals with this
case
(forcing the JAXP impl of XSLT to be used) provided that the JAXP
version does
not contain the bug.
However see issue #70130. It seems that the IBM JDK 1.5.0 bundles a
version of
Xalan which does suffer from XALANJ-2219. For that reason, NB currently
won't
run on this JDK, as it has no working XSLT processor available and
serialization
of namespaced XML is critical for the project system to work. If a fix for
XALANJ-2219 could be put into an update to the IBM JDK that would be
great. The
NB code already autodetects whether the JDK's Xalan has a fix for
XALANJ-2219 or
not (by testing its runtime behavior), so NB 5.0 ought to begin working
unmodified on a patched IBM JDK.
Thanks for the note! I know this situation is a bit complicated so feel
free to
contact me ([EMAIL PROTECTED]) if you need more information.
--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
