Currently this isn't easy, although it should be. Could you please raise a feature request in JIRA? As a workaround, it should be simple enough to override PermissionMapper.resolvePermission() to use a different ResolverChain.
Jira is done: https://jira.jboss.org/jira/browse/JBSEAM-3664
your workaround works but something is a bit dirty:
private ResolverChain getResolverChain(Object target, String action)
private ResolverChain createDefaultResolverChain()
and some attributes are private.
If I want to override public boolean resolvePermission(Object target, String action)
I need this methods too to get the aviable resolver. Is it possible to change this methods and the attributs form private to protected so that I don't need to copy this methods in my overriden class?
Making the resolver chain variables/methods protected will be part of the fix. Your overridden resolvePermission() method will have to implement the logic itself to use the correct ResolverChain instance. Another alternative if you already have a set order of resolvers that you wish to use for all permission checks is to simply hard code your own ResolverChain in the component's @Create method, and then use that.
I made my own ResolverChain now :)
thx a lot for your help!