On Fri, 19 Nov 2010 14:14:22 -0200, Everton Agner <ton.ag...@gmail.com>
wrote:
PS: About the Locale scenario, i don't know if you would need to have 2
page classes also.
No need for different page or component classes for different locales. One
page or component class, multiple templates, one for each locale.
Everton is right that a page or component can have zero templates. This is
more common with components that generate their output using MarkupWriter.
Btw, what's your scenario and why is the multiple templates per page a
requirement for you? Maybe you could achieve what you need with
Components...
I'm also curious to know what these requirements are. I never needed to
have more than one template for a given page or component. This sounds
like someone developing Tapestry with a Struts mind. :P
You can simulate multiple templates for a given page or component using
blocks (<t:block), components and the Delegate component.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
