Am Freitag, 19. Juni 2009 02:30:45 schrieb Thiago H. de Paula Figueiredo:
> As far as I can see, this is not a matter of Tapestry events, but of
> implementing a Template design pattern. ;)
>
> final Object onActivate(EventContext context) {
> initialize(context);
> }
>
> protected void initialize(EventContext context) {
> this.statusmessage = getUser().getStatusMessage();
> }
I thought about that as well - and the problem with that solution is that my
base class does not know about the activation context of its childs. Some
pages need two parameters, some need only one - sometimes it is an ID of
something, sometime it is the username. Its totally in the control of the page
how they initialize themselve.
For know I am calling initialize() in the onActivate(...) method of every
page. But my feeling is that there should be some framework provided
initialization method that is called AFTER page activation.
pageActivated() comes to mind.
Is this still something that doesnt make sense to you? (just to be sure I am
not on the completely wrong track).
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
