Policy data member in JaccAuthorizationInterceptor.java

[j2ee_junkie]

Currently org.jboss.ejb.plugins.JaccAuthorizationInterceptor stores the Policy obtained by the call to Policy.getPolicy() during setContainer() method. Java API for the getPolicy() method says not to cache this value as it may change. So if the setContainer call is made on each invocation, there is no concern. However, if the setContainer call is only made when the container is created, there could be a problem.

Does anyone know if the former or the latter is happing. Any pointers to where this happens would be nice to so I know for future reference.

thanks, cgriffith

[anil.saldhana]

Jacc policy currently is installed via the JaccAuthorizationRealm as part of the tomcat service. Since it is a VMwide policy, it does not matter. Once the policy is installed, you get it wherever you ask.

[anil.saldhana]

Regarding caching of policy, you do make a point. An anomoly will exist if somebody installs a policy in an MBean service via Policy.setPolicy call, which is different from the one that was installed by default as part of the JBoss startup.