David Marston wrote:
> The question was about referring to bundles of parameters when calling
> a named template repeatedly.
>
> You could do what you want if you used the node-set() extension
> function. The problem comes when you attempt
> <xsl:for-each select="$globalSettings/elem">
> where $globalSettings is a Result Tree Fragment, which cannot be used
> in a path expression.
>
> But there are a couple other questions to ask yourself:
> 1. Is the template you're calling doing extensive manipulations on its
> parameters to generate its final output? If not, think about breaking
> apart the named template into several, skipping the named template
> completely, using attribute-sets if the template emits attributes,
> etc. 2. (If #1 above is not feasible) Is there an advantage if you
> pass one parameter to the named template and have the template then
> step through a collection of values? There could be possibilities for
> xsl:key or packing values into strings, in addition to your approach
> built on global variables.
Thanks David, for your instant response. You got me onto the right path.
I've solved this issue by an elegant solution: Put my global definitions
(former globalSettings variable) into a separate xml file and read this
one by the document(.) function. Now I have a clear separation of
transform structure and transform symbol values, as well as nice and
short stylesheets. Thanks.
Axel
--
Humboldt-Universität zu Berlin
Institut für Informatik
Signalverarbeitung und Mustererkennung
Dipl.-Inf. Axel Weiß
Rudower Chaussee 25
12489 Berlin-Adlershof
+49-30-2093-3050
** www.freesp.de **
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
