> From: Johnny Kewl [mailto:[EMAIL PROTECTED] > Subject: Re: TOMCAT ISSUE: System.Exit > > yes it is a kludge, and I doubt very much whether changing > anything in catalina.policy will do anything in this case...
It's certainly not a kludge; one of the primary functions of a security manager is to prevent 3rd party classes used by your app from doing anything your app doesn't want it to do. Sounds like you need to do some reading about the Java security manager capability, and stop assuming things that simply aren't true. You are correct in thinking that changing catalina.policy won't have an effect, since that isn't used when Tomcat runs as embedded. You need to specify a security manager and your own policy file when the JVM starts. > because the security manager is probably > incorporated in the web-app class loader... It's not; a security manager is part of the core JVM, not associated with any particular class loader. That's why there can be only one security manager per JVM instance. > I'm trying to protect an embedded application FROM TOMCAT itself. No, you're trying to protect an application from an embedded Tomcat, which is exactly what security managers are intended for. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
