RE: [xsl] error: At xsl:choose, the value of "" is not a node-se t

["Clapham, Paul" <pclapham@xxxxxxxxxxxxx>]

It isn't an error to have two templates that operate on the same element.
If you do that, via xsl:include or otherwise, there is a set of priority
rules that determine which one will apply, the last of these rules being to
apply the last one appearing in the (merged) stylesheet.  In other words,
this is a feature instead of a bug, because you can use xsl:include to cause
templates in the includ-ee to override templates in the includ-er.

PC2

-----Original Message-----
From: Xiaocun Xu [mailto:xiaocunxu@xxxxxxxxx]
Sent: August 2, 2001 15:48
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] error: At xsl:choose, the value of "" is not a
node-set


Thanks for all the help, guys.  Sorry for not
mentioning the processor I use.  I currently use Saxon
6.0.2 (I know, I should be upgrading :(.  I will do
exactly that after finishing up this release of the
product).

After some investigation, the problem turned out to be
template name conflicts.  I had included a number of
XSL files in gXML2ePASS_base.xsl, and two of which had
the same template name operate on the same element.  I
modified them to use unique template names and now it
works fine.

My question is, how come it did not complain about
conflict template names during compile?  Does it
instead compiles each of the included XSL by itself?

Much thanks,
Xiaocun

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