Depending on your use case, you could either: 1. Contribute a ComponentRequestFilter to the ComponentRequestHandler or 2. Contribute a PageRenderRequestFilter to the PageRenderRequestHandler
Either way, the filter will push() an object onto the Environment which your pages / components can then access (by Environment.peek() or via the @Environmental annotation). Then your layout component (and other components) can make decisions based on the value of the Environmental object. http://tapestry.apache.org/environmental-services.html http://tapestry.apache.org/request-processing.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/layout-component-selection-based-on-domain-name-tp5719325p5719328.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
