Cart
[Home] [By Thread] [By Date] [Recent Entries]
Ibm not sure whether I have completely understood the scenario, but did
you consider using tunnel parameters?
https://www.w3.org/TR/xslt-30/#tunnel-params https://www.w3.org/TR/xslt20/#tunnel-params Calculate the variable once, in the context of a node that is ancestor-or-self to all affected nodes, and pass this variable as a tunnel parameter to apply-templates, to next-match, or to call-template. Gerrit On 7/18/2017 1:39 AM, Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx wrote: I am processing an xml doc where a template adds some elements at one point in the tree. While doing this, it generates a variable that I also use at another location in the tree. Rather than regenerate the variable and introduce a chance for breakage in the future, is there a more efficient approach for processing the alternate node without selecting that node and calling a template on it which needs to copy it? I need to call this same template several times?
|
