What you want is a more complex page name (+ other information) mapping to page class, but something fixed and predictable ... and properly cached, for performance reasons.
On Wed, Mar 9, 2011 at 1:08 AM, jqzone <jqz...@gmail.com> wrote: > I extending template locator just follow the link below,it works well. > http://blog.tapestry5.de/index.php/2010/08/06/extending-template-lookup-mechanism/ > > My situation is ,when the same page is requested,I should check the config > and decide which tml to use,for example ,different sub domains use different > tml, ComponentTemplateSource caches the first requested template,so how can > I change this? > -- 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: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
