Before 5.0.13, if onActivate() appeared in a subclass and its parent,
Tapestry used to jump in and call both. From 5.0.13 it seems to
follow the normal Java convention, ie. only the subclass method is
called, so it is up to the subclass to call the parent if that's what
you want. I ran a quick test a couple of days ago and I'm pretty sure
that's what I observed.
The result for me is that I've ditched my ProtectedPage superclass and
opted for a @ProtectedPage annotation instead in much the same way as http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess
. It's a pretty sweet solution.
Cheers,
Geoff
http://files.doublenegative.com.au/jumpstart
On 23/06/2008, at 10:54 AM, Thiago H. de Paula Figueiredo wrote:
Em Sun, 22 Jun 2008 04:09:30 -0300, Geoff Callender <[EMAIL PROTECTED]
> escreveu:
Furthermore, since T5.0.13, the parent class's onActivate() is no
longer called if it's been overridden in the child class (see https://issues.apache.org/jira/browse/TAPESTRY-2311
). Now you must ensure the child class's onActivate() calls
super.onActivate(), or else the security is lost. The approach is
looking pretty flimsy.
I don't think so. Why would overriden methods in Tapestry page class
behave differently from any other class around? I'm sorry, I just
couldn't follow the reasoning yet.
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
