Hi Ken,
You can use a base class. Just make your base class extend BasePage.
In my project too, we use a custom base class, which does exactly
what you described - abstract common code out. Using such a class,
also helps when you may need to add some hooks into your processing
(as many calls to pages) may be routed through your base class.
- Navin
On 30-Oct-06, at 7:50 PM, Ken nashua wrote:
Hi Folks,
Given the array of options of doing things... I am annotation
biased and prefer to define a base class that all my pages use that
performs things via annotation if possible.
1. I wonder what a base class would do to interfere with tapestry's
core processing though especially with regard to any reflection it
performs under the hood. Is it generally dangerous to implement a
base class that performs common operations (ex. provide get methods
for getHomePage() or getLoginPage(), getLogger(), getRole(), getUser
() etc...)
I am just trying to minimize the amount of code in my java classes.
If anyone could elaborate on this topic that would be terrific.
Thanks
_________________________________________________________________
Find a local pizza place, music store, museum and more
then map the best route! http://local.live.com?FORM=MGA001
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
