That's not the problem. If I comment out "ServletContextListener" interface, I still don't get any session notifications.
On Wed, 2002-09-11 at 04:23, Chris Brown wrote: > > You seem to have implemented the correct interfaces. However, I've not seen > your web.xml deployment descriptor. You'll need to refer to your class in > two separate places in web.xml in order for both event types (session and > application) to be sent to your class. I suspect that the servlet engine > will create one separate instance of the class for listening to application > start/stop and another for session activation/deactivation. > > If you really need to store everything in one instance of the class, you > could always add "this" (the servlet context listener) as a servlet context > attribute, and then when a session starts or ends, call a method of the > "first" instance by getting the copy you put in the servlet context. I'd > personally make two classes, for readability and simplicity though! > > - Chris > > ----- Original Message ----- > From: "Felipe Schnack" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, September 10, 2002 8:14 PM > Subject: Re: global.jsa > > > > Hi! > > I saw this post of yours in the tomcat list and tried myself. For some > > reason it doesn works... you can help me? I don't know what to do, it > > works for application start/stop, but not for session. > > > > On Mon, 2002-09-09 at 05:51, Chris Brown wrote: > > > > > > Hello, > > > > > > I've seen a few answers to your question suggesting that you use a > servlet > > > that loads on startup. I have another suggestion that you may prefer to > > > emulate "global.asa": implement ServletContextListener and > > > HttpSessionActivationListener. > > > > > > javax.servlet.ServletContextListener > > > > > > ...sends you events when the webapp starts and ends. > > > > > > javax.servlet.http.HttpSessionActivationListener > > > > > > ...sends you events when a session is created or destroyed. > > > > > > You'll find javadocs for these items in the following path with a > default > > > tomcat installation, obviously relative to the root of your > installation: > > > > > > /tomcat-docs/servletapi/index.html > > > > > > To use them, you'll need to add appropriate XML elements to web.xml > (refer > > > to a tutorial or the web.xml DTD). It's simple and works well. > > > > > > - Chris > > > > > > ----- Original Message ----- > > > From: "neal" <[EMAIL PROTECTED]> > > > To: "Tomcat Users List" <[EMAIL PROTECTED]> > > > Sent: Tuesday, September 03, 2002 10:14 AM > > > Subject: global.jsa > > > > > > > > > > Is there such a thing as a global.jsa file in Tomcat? > > > > > > > > I first saw this concept (an idea taken from ASP's global.asa) > implemented > > > > in JRUN. > > > > > > > > If there is a global.jsa, does anyone know of any docs on this? If > not, > > > is > > > > there an alternative? The reason I would want to use this is to > > > instantiate, > > > > populate, and cache a few objects upon startup of the application. If > > > > Tomcat does not provide a global.jsa...does anyone know how otherwise > to > > > > achieve the goal? > > > > > > > > Thanks. > > > > Neal > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > -- > > > > Felipe Schnack > > Analista de Sistemas > > [EMAIL PROTECTED] > > Cel.: (51)91287530 > > Linux Counter #281893 > > > > Faculdade Ritter dos Reis > > www.ritterdosreis.br > > [EMAIL PROTECTED] > > Fone/Fax.: (51)32303328 > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Felipe Schnack Analista de Sistemas [EMAIL PROTECTED] Cel.: (51)91287530 Linux Counter #281893 Faculdade Ritter dos Reis www.ritterdosreis.br [EMAIL PROTECTED] Fone/Fax.: (51)32303328 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
