That helps. If you don't want to use it, pretty much the only way to
achieve what was requested is by a two-stage process.
Stage 1 would run a stylesheet on the configuration document
to generate a
stylesheet.
Stage 2 would run the resulting stylesheet on the source document(s).
Using saxon:evaluate should allow you to do it in one pass.
It's a little bit trickier than that, because the XPath expression
identified elements to be modified. Evaluating a dynamic XPath expression to
give a set of nodes is one thing; writing a stylesheet that modifies the
nodes in the result of that expression is another.
Also there are multiple expressions, and doing one pass (i.e. a document
copy) for each expression sounds expensive.
If the expressions are constrained to be XSLT patterns, then it would
probably be easier to generate a stylesheet dynamically in this situation.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--