Hi Angelo, I am probably over simplifying things, but think of it like this, Activate is analogous to a Get request, so is invoked when a page first loads, passivate is called after a Post (to ensure the posted page retains those activation parameters)... passivate does not correspond to activate in a 1:1 cycle, as posts can occur for any number of components / form events.
Cheers, Peter ----- Original Message ----- From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Tuesday, 17 February, 2009 17:06:44 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: t5: onActivate called twice On Tue, Feb 17, 2009 at 12:02 PM, Angelo Chen <angelochen...@yahoo.com.hk> wrote: > you need a onPassivate to persist the context on the client side if: You need an onPassivate() method to tell Tapestry what is the activation context for a given page. This is needed primarily because of redirect-after-post, AFAIK, and every time Tapestry needs to generate a link for a page. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
