By overriding internal services (and a bit of cut-n-paste) you can accomplish this kind of thing.
I hope to make it easier in Tapestry 5.2 by splitting a few bigger services into smaller ones, to isolate the little bit of logic that needs to be overridden. Further discussion to the user mailing list. On Thu, Jul 9, 2009 at 3:25 PM, JUDr. Matthew Plansky<s...@zoznam.sk> wrote: > Hi Howard , > is it possible to set a special template(.tml) location for some pages or > components? > > Example: > dir/SuperPage.class - has 3 tml: > dir/anytmldirA/SuperPageTemplate.tml > dir/anytmldirB/SuperPageTemplate.tml > dir/anytmldirC/SuperPageTemplate.tml > > ...which template will be used, can be stored in dbs. > > Is there any possibility, whatever, to set tml location for the page during > app startup, or during running? > > thank you very very very very very very very very very very very very > very much for any response > -- > Best regards, > JUDr. Matthew Plansky mailto:s...@zoznam.sk > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
