The easy solution is, don't use private variables like that. Declare them as persistent page properties. Do your development with caching disabled so that the problem appears right away, rather than after a ten-minute garbage-collection period.
Mark Stang wrote: > Hi, > I am seeing Tapestry 3 components with values which is good, say a ArrayList: > > private ArrayList<ConnectionItem> displayList; > > If I don't touch the component for 10 minutes or maybe a little longer, then > the "displayList" is null. I assume that this is due to Tapestry putting it > back in the pool. However, I then get a NPE. Any idea where I can set the > timeout? Or if I can find a way to disable it. What I have to do is put a > null check around access to the variable and then re-create the list if it is > null. > > thanks, > > Mark > > Mark J. Stang > Senior Engineer/Architect > office: +1 303.468.2900 > mobile: +1 303.507.2833 > Ping Identity > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
