RE: load-on-startup

2008-11-25 Thread Caldarale, Charles R
> From: André Warnier [mailto:[EMAIL PROTECTED] > Subject: load-on-startup > > 1) In the case of Tomcat 5.5 and higher, is there a way to *prevent* a > deployed application to be loaded and/or started at Tomcat startup ? Turn off the deployOnStartup attributes of the element.

Re: load-on-startup

2008-11-25 Thread Juha Laiho
t startup ? > (basically only be started when the first call to it is made) I don't think so. However, if you don't have load-on-startup at all, the servlets will only be loaded when first referenced. As to when the JSP compilation happens, I'm not certain (but once compiled, I think

load-on-startup

2008-11-25 Thread André Warnier
Hi. About the item in web.xml, the Servlet Spec 2.5 has this to say (p 128) : The load-on-startup element indicates that this servlet should be loaded (instantiated and have its init() called) on the startup of the web application. The optional contents of these element must be an integer

Re: load-on-startup problem

2007-11-15 Thread Christopher Schultz
cated: use a ServletContextListener instead. > Couple of days ago I moved my project to another > computer on a new tomcat installation and after a while I decided to > remove the load on startup tag from web.xml and I also deleted the > code in the init() method in my servlet. Weird thin

load-on-startup problem

2007-11-15 Thread loredana loredana
trying to load the servlet on startup? deleting load-on startup from web.xml is not enough? do I still have to configure something else? 10x a lot Be a better sports nut! Let your teams follow you with

Re: Listener vs. load-on-startup

2007-04-24 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lizhg, lizhg wrote: > Hi all, I have some problem with Listener and load-on-startup, I search > on google and I find this article below, it do a lot good to me, but I > still want to ask , using the init() [and destroy()] of a servlet >

Re: Listener vs. load-on-startup

2007-04-24 Thread Jon Wingfield
The order of events is: Startup: All listeners get called. All filters, load-on-startup servlets get inited. Shutdown: All filters, servlets get destroyed. All listeners get called. So, it is possible for the combination of load-on-startup init + contextDestroyed to do the same job as just using

Listener vs. load-on-startup

2007-04-23 Thread lizhg
Hi all,I have some problem with Listener and load-on-startup,I serch on google and I find this article below,it do a lot good to me, but I still want to ask , using the init() of a servlet and the contextDestroyed() of a listener are equal to Iusing the contexInitialized() and the

Re: multiple instances of load-on-startup classes

2006-06-27 Thread Magnus Larsgården
either. I really think that this is a serious bug... BR Magnus - Original Message - From: "dirk ooms" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Tuesday, June 27, 2006 3:04 PM Subject: Re: multiple instances of load-on-startup classes i had someth

Re: multiple instances of load-on-startup classes

2006-06-27 Thread dirk ooms
wrote: > We have a webapp running within Tomcat 5.0.28 on Linux. > The message log indicates that any classes are loaded > twice. Also, any singleton objects created by these load-on-startup classes > are created twice. This has been confirmed by stepping through the code via

multiple instances of load-on-startup classes

2006-06-27 Thread Mark Benussi
We have a webapp running within Tomcat 5.0.28 on Linux. The message log indicates that any classes are loaded twice. Also, any singleton objects created by these load-on-startup classes are created twice. This has been confirmed by stepping through the code via a debugger. From what I have