Pablo, Thiago, Thanks for the responses. Thiago, the idea of the utility methods also being available outside a page is a good enough reason for me to move them into a service. Thanks for the pointer.
Regards, Jim. -----Original Message----- From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 19 July 2010 15:59 To: Tapestry users Subject: Re: Best practise for bloated utility methods location 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
