The practical application is to allow per-client skinning of compoonents by replacing their templates with alternate templates from a different location. Anyway, that's what Widen uses it for, and that's why I implemented it. In theory, it lets you access templates from any location that can be represented as a Resource.
On Thu, May 20, 2010 at 2:12 AM, Massimo Lusetti <[email protected]> wrote: > On Thu, May 20, 2010 at 2:19 AM, <[email protected]> wrote: > >> Author: hlship >> Date: Thu May 20 00:19:04 2010 >> New Revision: 946492 >> >> URL: http://svn.apache.org/viewvc?rev=946492&view=rev >> Log: >> TAP5-1159: Easy way to customize search locations for page and component >> templates > > Wow what a change! > Am I the only one seeing this as a big change and a big plus !? > > Cheers > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
