DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6660>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6660 Catalina with SecurityManager is possibly broken. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2002-02-25 18:36 ------- The implementation of the Java SecurityManager is significantly different between Tomcat 3.2/3.3 and Tomcat 4. The Tomcat 4 version implements much finer control over granting permissions in the policy file. Even down to granting permisions to individual classes within a jar. jar's in /WEB-INF/lib have a completely different codeBase than classes in /WEB-INF/classes. To fix your problem add the following grant to your catalina.policy grant codeBase "jar:file:{path-to-webapp}/WEB-INF/lib/WriteFile.jar!/-" { permission java.io.FilePermission "/home/client/-", "read,write,delete"; permission java.util.PropertyPermission "*", "read"; }; -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
