-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael,
Michael Ludwig wrote: > The very fact that object leak from one web app into another is a > possibility seems to constitute a strong argument in favour of strict > monitoring, be it only to shield oneself from errors that might be > difficult to track down. It's rare that an object would "leak" from one app to another. When Chuck says "more global", he means in the classloader-sense. That typically means that the object would be passed from the webapp to the container, which is usually a safe operation. If you want to pass objects between webapps, you will have to provide the JAR files containing their classes to a class loader that is higher than both webapps. > May I rephrase this into there being a duty for the Tomcat admin to > enforce none of the web apps loaded into his container supply a library > that the container itself already supplies? That's a reasonable request, but is often easier said than done. Since webapps can come with any variety of JAR files (or even re-packaged JAR files) it might not be possible to enforce this rule. But, if your webapp breaks the rules, something usually goes wrong (like a ClassCastException) so the webapp suffers, anyway ;) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk0VEEACgkQ9CaO5/Lv0PA0NQCdF79iMNz/qlNC8yderBceFgeL rXkAoMLjJY3kclOc16NiAm04fLvPtERc =tlE8 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
