I know about what you said. I am thinking whether there was any other reason why the objectfactory approach was chosen, like some customer wanting to do "java:/jaas/securitydomain/cache-policy" to get to the cache policy instance or such. I think the simpler approach is just to inject the FQN of the cache policy implementation into the jaassecmgr mbean service. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093695#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...