For now it appears that moving the code to pageValidate() might just do the trick. But am a little uncertain about the page lifecycle
Any expert-opinions? On 8/3/06, Karthik N <[EMAIL PROTECTED]> wrote:
I believe initialize is called when the page is infact retrieved from the pool. however pageBeginRender is called only if there's something to render. since for direct links pageBeginRender is not called, we're in a mess right now. On 8/3/06, Norbert Sándor <[EMAIL PROTECTED]> wrote: > > As I remember (I used it very rarely) initialize() was called when the > page was put back into the pool. > So isn't PageDetachListener is more appropriate to replace initialize()? > > Sorry if I'm wrong :) > > Regards, > Norbi > > Karthik N wrote: > > We have some code in the initialize() method. Per the 4.1 doc > > initialize() > > is deprecated and we've to move the code to pageBeginRender(). > > > > however we find that code in the pageBeginRender does **not** get > invoked > > for direct links, which is correct behavior. > > > > and hence we end up with all sorts of issues due to uninitialized > > properties > > when direct links are invoked. > > > > so is it our improper usage of initialize(), or should initialize() > > not be > > deprecated?!! > > > > Thanks, Karthik > > > > > ------------------------------------------------------------------------ > > > > No virus found in this incoming message. > > Checked by AVG Free Edition. > > Version: 7.1.394 / Virus Database: 268.10.5/406 - Release Date: > 2006.08.02. > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks, Karthik
-- Thanks, Karthik
