Hi all, I'm deploying axis2 (war) in a Tomcat5 container (on Debian Sarge), and the Java security manager presents me with read/write permission errors when accessing the validation page. They are fixed by adding following lines to /etc/tomcat5/policy.d/04webapps.policy : permission java.util.PropertyPermission "om.factory", "read"; permission java.util.PropertyPermission "axis2.home", "read"; permission java.util.PropertyPermission "user.home", "read"; permission java.io.FilePermission "/usr/share/tomcat5/.axis2", "read"; permission java.io.FilePermission "/usr/share/tomcat5/.axis2", "write"; permission java.io.FilePermission "/usr/share/tomcat5/.axis2/*", "read"; permission java.io.FilePermission "/usr/share/tomcat5/.axis2/*", "write"; permission java.io.FilePermission "/usr/share/tomcat5", "read"; permission java.io.FilePermission "/var/lib/tomcat5/work/Catalina/localhost/axis2/loader/META-INF/MANIFEST.MF", "write"; permission java.io.FilePermission "/var/lib/tomcat5/work/Catalina/localhost/axis2/loader/org/apache/axis2/deployment", "write"; permission java.io.FilePermission "/var/cache/tomcat5/Catalina/localhost/axis2/loader/org/apache/axis2", "write"; permission java.io.FilePermission "/var/lib/tomcat5/work/Catalina/localhost/axis2/loader/org/apache/axis2/deployment/axis2.xml", "write";
<etc> Clearly, this isn't the right solution. Can someone tell me how I tell the security manager to let axis2 do it's thing? Disabling the security manager is not an option to me. thanks, Bram
