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]
