FYI one bonus of using @PageActivationContext is that you automatically
have onPassivate() generated for you. If you declare onActivate() you'll
need to do this yourself
On 20 Sep 2016 5:56 p.m., "Thiago H de Paula Figueiredo" <thiag...@gmail.com>
wrote:
> On Tue, 20 Sep 2016 13:24:08 -0300, Nathan Quirynen <
> nat...@pensionarchitects.be> wrote:
>
> |You can do something like the following: void onActivate(EventContext
>> eventContext) { |
>> ||if(eventContext.getCount() == 1) { ... } ||||if(eventContext.getCount()
>> == 2) { ... } ||||if(eventContext.getCount() == 3) { ... } ... |||||
>>
>> } |
>>
>
> Exactly. If you end up having more than one onActivate() in the same page
> class, you should instead have just one with a single EventContenxt
> parameter.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
