You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2010/02/02 06:32:20 UTC

[jira] Assigned: (SHIRO-59) Refactor Realm implementations to favor delegation over inheritance

     [ https://issues.apache.org/jira/browse/SHIRO-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kalle Korhonen reassigned SHIRO-59:
-----------------------------------

    Assignee: Kalle Korhonen

> Refactor Realm implementations to favor delegation over inheritance
> -------------------------------------------------------------------
>
>                 Key: SHIRO-59
>                 URL: https://issues.apache.org/jira/browse/SHIRO-59
>             Project: Shiro
>          Issue Type: Improvement
>            Reporter: Les Hazlewood
>            Assignee: Kalle Korhonen
>         Attachments: SHIRO-59.diff
>
>
> Currently most people need to subclass Realm implementations to perform role and/or permission checks.  This is not very scalable when more than a few realms exist, or people need to re-use realms across applications.
> Instead, it would be much nicer to allow developers to configure components that did most of the common Realm logic, regardless of data store.  For example, perhaps a RolePermissionResolver could be introduced:
> rolePermissionResolver.getPermissions( String roleName );
> This could be injected across multiple realms across applications instead of needing to subclass Realm implementations - a little nicer approach.  Also, we might want to look at uses of the Strategy design pattern for checking logic.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.