For the record, I also get this behaviour. I suppose the only foolproof
method is to have the getter for the property to check for nulls and to
initialise the property again if it is null.
Dan
Edward Scanzano wrote:
Hi all,
I have a situtation where my application runs normally
as I click through it. Parameters are being passed to
components correctly, etc. However, if I let the
application sit idle for a short time (maybe 10
minutes, not sure of the exact time) then when I click
on those same links I get exceptions that are caused
by component parameters being null. The session has
not timed out yet.
What is causing this?
Thanks
E
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
