rom: Eric Larson <[EMAIL PROTECTED]>
> >Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
> >To: Tomcat Users List <[EMAIL PROTECTED]>
> >Subject: Re: application scope question
> >Date: Sun, 16 Mar 2003 20:57:59 -0500
> >
> >
> &
instantiated?
mike
From: Eric Larson <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
To: Tomcat Users List <[EMAIL PROTECTED]>
Subject: Re: application scope question
Date: Sun, 16 Mar 2003 20:57:59 -0500
The session bean doesn't actually
The session bean doesn't actually expire when the browser window is
closed. It times out at some point in the future when it hasn't been
accessed for some number of minutes that you can configure.
Theoretically you could manipulate session beans using Listeners to gain
access to the beans after th
Application scope lasts for the life of the webapp. A webapps ends when
either:
a) Tomcat stops running
b) The machine stop running
c) The webapp is restarted
-Tim
Michael Ni wrote:
for usebean, i know the bean expires for scope session when the browser
is closed. but for scope application, wh
for usebean, i know the bean expires for scope session when the browser is
closed. but for scope application, when does the bean expire? does it keep
running even after the person who called the bean exits his browser? if so,
how can the bean terminate itself in an application scope.
mike
_
