I prefer to avoid base classes so I package such utility methods into
one or more services and just freely inject those services into my
pages and/or components.
On Mon, Jul 19, 2010 at 7:24 AM, Jim O'Callaghan
wrote:
> I have a 'base' Page class that has behaviour used throughout a large
> secti
...@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
wrote:
> I have a 'base' Page class that has behaviour used throughout a large
> section of appl
On Mon, 19 Jul 2010 11:24:20 -0300, Jim O'Callaghan
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 extr
Hi Jim,
Where I work the apporoach is like this:
"Base Pages" are used for prevent some duplicates methods that returns
models, enconder or same actions to remove or include.
Services are used to actions in the business.
But this approach not consider efficiency and it's only a pattern.
2010/7
