Re: [Wonder-disc] Ajax requests and component life-cycle

[Paul H. <pa...@lo...>]

I'll stop replying to myself shortly.

On 14/06/2009, at 5:58 PM, Paul Hoadley wrote:

> 2.  It looks like I can work around it by using
> AjaxUtils.isAjaxRequest() and not clearing the array on the first call
> to sleep().  Any opinions on whether this is safe?

Here's an opinion: it doesn't work.  From what I can tell, and correct  
me if I am wrong, an AUC update will actually walk the entire  
component graph, not just the graph rooted at the AUC itself.  Even if  
that assumption is wrong, I am now seeing a varying number of calls to  
sleep() on my "one-shot" component, varying with the number of  
containers I get my AjaxUpdateTrigger to update.  So assuming there  
will be two calls to sleep() in an Ajax request doesn't work.

So I'm left with this:

> Does anyone have any better suggestions for how to make a "one-shot"  
> component like this?

Basically, I want it to clear after one _actual rendering to the  
browser_.  It seems I can't rely on sleep() to clear the data.  Is  
there another way?


-- 
Paul.

w  http://logicsquad.net/
h  http://paul.hoadley.name/