> 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
----- Original Message -----
From: "xfile80303" <l...@grokers.net>
To: users@tapestry.apache.org
Sent: Wednesday, 18 February, 2009 02:35:03 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: Re: [T5] Struggling With Concepts
Fernando Padilla wrote:
>
> Ok, here is an example.. hope it's legible. :) The meat of the code is
> the ContextFilterRequest below. If you create a normal J2EE filter that
> determines what part of the path to rip out, then if can do:
>
Thanks Fernando, I appreciate you taking the time.
--
View this message in context:
http://n2.nabble.com/-T5--Struggling-With-Concepts-tp2324920p2344202.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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
