[xsl] (possible) strange behaviour of JD.xslt

Subject: [xsl] (possible) strange behaviour of JD.xslt
From: "Rubén Martínez" <rubenm@xxxxxxxxxxxxx>
Date: Wed, 07 Nov 2001 18:17:39 +0100
Hi all,

I'm trying to get a javax.xml.transform.Transformer from the xsl:

<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
version="1.0" xml:space="preserve">
<xsl:output method="xml" omit-xml-declaration="yes"/>
<xsl:template match="/">
   <xsl:when test="*some text*">Value 1</xsl:when>
   <xsl:otherwise>Value 2</xsl:otherwise>

I can do that with many XSLT processors but I would like to use JD.xslt
(I've found it the fastest processor made in Java). This processor throws
the message: "Invalid child node 'null' for a xsl:choose element". If I
remove the attribute *xml:space="preserve"* or I write no whitespaces
between tags <xsl:choose>,<xsl:when> and <xsl:otherwise> all works fine.

I guess the JD.xslt builds a tree from this xsl file with some text nodes
(whose node value is several spaces and node name is null), and when it
checks the childs of <xsl:choose> only allows <xsl:when> and
<xsl:otherwise> but it finds this text nodes.

My problem is that I have hundreds of legacy xsls and changing all wouldn't
be trivial, and my question:

Does anyone know if the XSLT specification or something say that <xsl:when>
must follow <xsl:choose> without whitespaces between them when
xml:space="preserve" is used, or is this a bug of JD.xslt?

Thanks in advance and sorry for my poor english.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Current Thread