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

Subject: Re: [xsl] workaround for XSLT 1.0 result tree fragment usage?
From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>
Date: Wed, 19 Dec 2007 12:31:32 -0500

In addition to using an extension function to cast the result tree fragment into a node set, another solution is also sometimes possible, since while RTFs can't be interrogated as node-sets, they can be processed as strings.

So if you built your variable like this:


you could simply test "not(contains($confirm_active_program,'true'))" and that would work.

Of course this doesn't scale to more complex situations, but it's good enough for many simple ones.


At 09:53 AM 12/19/2007, you wrote:
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.

Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.      
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
  Mulberry Technologies: A Consultancy Specializing in SGML and XML

Current Thread