I totally agree with Thiago... you are trying to break tapestry's (very
sensible) principles.
Take a look at the link I sent you originally... pass a component parameter
(not a request parameter) from the page to the layout or use the
Environment.
On 2 May 2012 21:06, netdawg <net.d...@yahoo.com> wrote:
> OK...I think I got it...this works...swapping the property to the component
> instead and have it intercept the page request
>
>
> <htmlelement id="${pageProperty}" />
> <t:body />
>
> Layout.java :
> public class Layout
> {
> @ActivationRequestParameter
> @Property
> private String pageProperty= "default";
> }
>
>
> Index.java is now empty
>
> But Index page will have to be called by invoked index?pageProperty=
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Can-Component-Template-be-Informed-by-Page-Class-tp5681397p5681501.html
> Sent from the Tapestry - User 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
>
>
