[xsl] workaround for XSLT 1.0 result tree fragment usage?

Subject: [xsl] workaround for XSLT 1.0 result tree fragment usage?
From: Don Smith <dsmith_lockesmith@xxxxxxxxx>
Date: Wed, 19 Dec 2007 06:53:10 -0800 (PST)
I know the real answer to my question is to move to
XSLT 2.0, but for the sake of workplace harmony I'm
making other efforts as well.

Using XSLT 1.0 and MSXML I've run into the limitation
of an improper use of a result tree fragment. I'm
creating a variable, "confirm_active_program" that
contains some number of <program> elements like so:

<program active="true"/>
<program active="false"/>

I then have a choose statement which contains a when

test="not($confirm_active_program/program[@active =

The only error I'm getting is that the expression
requires a node-set. Going back and reading on RTFs in
1.0 I realize this isn't going to work. Is there any
other way to accomplish my desired effect in 1.0?



Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

Current Thread