With the current setup, the protection domain that is failing is: | ProtectionDomain (vfszip:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.GA/lib/jboss-aop-asintegration-core.jar <no signer certificates>) | null | <no principals> | java.security.Permissions@12910b0b ( | (java.net.SocketPermission * connect,resolve) | (java.lang.RuntimePermission getClassLoader) | (java.lang.RuntimePermission accessClassInPackage.*) | (java.lang.RuntimePermission org.jboss.security.SecurityAssociation.getSubject) | (java.lang.RuntimePermission queuePrintJob) | (java.lang.RuntimePermission getProtectionDomain) | (java.util.PropertyPermission * read) | (javax.management.MBeanServerPermission findMBeanServer) | (javax.management.MBeanPermission org.jboss.mx.modelmbean.XMBean#*[JMImplementation:type=MBeanRegistry] *) | (javax.management.MBeanPermission org.jboss.security.plugins.JaasSecurityManagerService#*[jboss.security:service=JaasSecurityManager] invoke) | (javax.management.MBeanPermission org.jboss.security.plugins.AuthorizationManagerService#*[jboss.security:service=AuthorizationManager] invoke) | (javax.management.MBeanPermission org.jboss.security.auth.login.XMLLoginConfig#*[jboss.security:service=XMLLoginConfig] invoke) | (javax.security.auth.AuthPermission createLoginContext.*) | (javax.security.auth.AuthPermission getLoginConfiguration) | (java.io.FilePermission file:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.GA/bin/../server/default/tmp/- read) | (java.io.FilePermission file:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.GA/server/default/tmp/- read) | (java.security.SecurityPermission getPolicy) | ) | | I tried the protocol handler approach to apply the vfszip handler. No luck. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187596#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...