[SHIRO-59] Refactor Realm implementations to favor delegation over inheritance

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Assignee: Kalle Korhonen
• Reporter: Les Hazlewood
• Created: 27/Apr/09 19:44
• Updated: 11/Jun/10 22:00
• Resolved: 14/Feb/10 01:51

Description

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.

Issue Links

• is related to: SHIRO-163 ModularRealmAuthorizer.setRealms needs to call applyRolePermissionResolverToRealms