This issue does not exist in JBoss 4.x, because the JACC permissions were created in the
tomcat/ejb deployers. In 5.x, we create them externally in the security deployers (because
the deployment life cycle dictates the lifecycle of the jacc permissions for a
deployment).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175146#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...