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. .................David Marston --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
