Hi Peter, But, if I follow you correctly, there will still need to be a class, even if empty, with the desired path as its package for every "site." I'm trying to make the site a dynamic configuration which does not need the addition of more pages.
Cheers, Levi Peter Stavrinides wrote: > >> They will all use the same pages and page flow, but will key >> off of the site name > Sorry but I don't get this comment? I mean what exactly are you trying to > do?... Tapestry uses composition, so construct components instead of > pages,, embed those components in your pages (just empty containers > really, with different settings, "parameters", you duplicate nothing this > way), set a site parameter in your component according, whose value > corresponds with the containing page (your site /sub-section), and thats > it. > > component A (shared) > / \ > page 1 (@parameter site = A) page 2 (@parameter site=B) > > cheers, > Peter > -- View this message in context: http://n2.nabble.com/-T5--Struggling-With-Concepts-tp2324920p2348095.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
