[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Nicer way to change context-node than xsl:for-each

Subject: Re: Nicer way to change context-node than xsl:for-each ?
From: David Carlisle <davidc@xxxxxxxxx>
Date: Sat, 5 Dec 2009 11:14:51 GMT
Re:  Nicer way to change context-node than xsl:for-each
> If a change in context was required for call-template, I might have
> modeled this, by having another parameter for *[1] on call-template
> (which might be a better design decision, as it encourages loose
> coupling!), instead of modeling this requirement as a loop.

yes or make it a match template instead of named. But still It's not
uncommon for me to find myself with a largeish called template with,
within its code lots of implicit assumtions on the current nde. And when
you find yourself needing to call that in another context wrapping it in
xsl:for-each is often the least intrusive change.


The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.