This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
using a parameter as filterexpression element
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: [xsl] using a parameter as filterexpression element
- From: "Mattias Konradsson" <preacher at fragzone dot se>
- Date: Fri, 1 Jun 2001 12:47:18 +0200
- References: <DD3244BDF5B4D411BB9D0060948A3B630162BC4B@IGMAIL4> <150647306878.20010601082259@jenitennison.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
hmm, tricky this, I have an variable like this
<xsl:variable name="selection_all" select="//header[Sender =
$current_user]"/>
and want to make it so that instead of the Sender element in the filter it
takes a the element to filter against as an parameter, like
<xsl:variable name="selection_all" select="//header[$TheElement =
$current_user]"/>
doesnt work of course, and I'd guess this doesn't work either:
<xsl:variable name="selection_all" select="//header[[local-name() =
$TheElement] = $current_user]"/>
so, is it possible to pass both the element and the element value in a
filter?
Best Regards
---
Mattias Konradsson
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list