-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck,
On 3/13/2009 11:34 AM, Caldarale, Charles R wrote: >> From: Christopher Schultz [mailto:ch...@christopherschultz.net] >> Subject: Re: Tomcat for Dummies >> >> You can even restart the manager app > > Nit picking: probably not. It looks like the manager app does all > the > work of starting and stopping other webapps, so there doesn't appear to > be any threads running around to do the work for you. You could have > some other app restart the manager, but then you've basically just > reimplemented the manager. Auto-deploy is probably the only other means > of restarting the manager. Right. To be clear: I just meant that the manager app is just somewhat special. Taking it down (or back up) won't affect any other webapps. >> When Tomcat deploys a webapp, it creates a ClassLoader >> for that webapp that tries to load all classes from that >> webapp's WEB-INF/classes filter and JAR files within >> WEB-INF/lib. > > Such loading actually only occurs when needed, not at deployment, > other than for listeners and servlets marked as load-on-startup. > Consequently, missing classes may not be found for quite some time. I suppose I was missing some parentheses. What I meant was: " When Tomcat deploys a webapp, it creates a ClassLoader for that webapp (that tries to load all classes from that webapp's WEB-INF/classes filter and JAR files within WEB-INF/lib). " I didn't mean to imply that all classes were speculatively loaded. They are loaded on demand. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm6ilUACgkQ9CaO5/Lv0PAjzACghxABFimn2ny+Rle9TIjvblum oYgAn2mAdHdVvlSzp6arli0e9krXVzHw =9LWP -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
