Re: [xsl] top level params and xsl:attribute magic?

[Dimitre Novatchev <dnovatchev@xxxxxxxxx>]

"S Woodside" <sbwoodside@xxxxxxxxx> wrote in message
news:5946E590-2B28-11D7-8385-000393414368@xxxxxxxxxxxx
> I have to, the param arrives as a string, not a node set, and XSLT
has 
> no built-in way to convert the first to the second. Per the thread a 
> few days ago.
> 
> simon
> 
> On Saturday, January 18, 2003, at 02:08  AM, Dimitre Novatchev wrote:
> 
> > First, I would stroongly recommend *not* to use any xx:evaluate
> > function.
> >

Please, read well. Obviously, you didn't understand my message.

What I think is the best solution of your problem is to set the value
of the "select" attribute of a global xsl:param to the *string* XPath
expression. You can do this using the selectSingleNode() and then
setAttribute() methods. Then perform the transformation.

Where did I say you had to pass a node-set? Just set the "select"
attribute to the *string* that is the specific XPath expression.

This is the general approach where one uses a *skeleton* stylesheet and
"fills-in-the-blanks" just before the stylesheet has to be applied.

This is why in most cases there is no real need for a xx:evaluate()
function.




=====
Cheers,

Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

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