2012/11/14 Christopher Schultz <ch...@christopherschultz.net>: > >> Do you have any idea why old jasper-compiler (used inside an >> application) provoke errors to other applications? Is it a bug? Or >> is there some additional config to make it works? > > Oh, this breaks *other* applications? There may be some weirdness, > here, because Tomcat internals might be polluted by classes loaded > from a particular webapp. That definitely shouldn't happen if we can > help it. >
It is a feature. If your webapps are bad citizens and do stupid things or you need protection from them, run with SecurityManager being enabled. Unless you run with SecurityManager, there is no protection against any webapp messing up with Tomcat internals, Java internals, or messing up with your operating system as a whole (limited only by the rights that tomcat user has). Note that if you run with SecurityManager, you have to pay the performance price for all those little checks that it does. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
