Nick,
I don't think I have caching disabled. I think, and I am trying to prove it
now, that what happens is that it has to do with assigning a bound value and
then somehow the bound value times out. I think that if I directly access the
custom property without assigning it to a local variable it will be fine. I
don't understand the timing issue though. Is there a Tapestry timeout of 5-6
minutes in there? Could it be that the component was put back in the pool and
the variable was set to null? The solution I am trying is to always access the
value via:
private ArrayList<ConnectionItem> getConnections()
{
return
(ArrayList<ConnectionItem>)getConnectionsBinding().getObject("connections",
ArrayList.class);
}
Does this make sense to anyone?
thanks,
Mark
-----Original Message-----
From: Nick Westgate [mailto:[EMAIL PROTECTED]
Sent: Tue 5/2/2006 1:59 AM
To: Tapestry development
Subject: Re: 3.x timeouts?
Hi Mark.
I've seen this behaviour when caching is disabled.
Is that the case for you? Even so, I've not looked
into why it happens - in production it works fine.
Cheers,
Nick.
Mark Stang wrote:
> Hi,
> I am posting this to the Developer list because I need to understand what is
> happening under the covers. I have a component that has an ArrayList passed
> into it as "custom".
>
> I display the ArrayList using a Foreach. I have "edit links". They are
> DirectLinks. If I wait about 6 minutes and then click on a link I get a null
> pointer exception. I have tracked the NPE to be because array list is null.
> However, the component drew the list and the links that I am clicking. So,
> where did my list go?
>
> thanks,
>
> Mark
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
