On Mon, 19 Jul 2010 11:24:20 -0300, Jim O'Callaghan
<j...@peritussolutions.com> wrote:
I have a 'base' Page class that has behaviour used throughout a large
section of application pages, and is extended by them. It's starting to
get a bit bloated with utility methods. Is it better practise / more
efficient to extract these utility methods from the base page class and
put them in a helper service, that can be injected into pages, or is
there any advantage / disadvantage to either approach? Any first-hand
experience of pros / cons of each approach? Thanks.
I think the approach of coding utility methods in services is the best
one. Services are more flexible than pages, and methods in services can be
used outside pages as well.
--
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
