[TRB-40] Fulcrum Security-API uses objects where it should provide interfaces

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Core 4.0-M1
• Fix Version/s: Core 4.0-M1
• Component/s: Fulcrum
• Assignee: Thomas Vandahl
• Reporter: Thomas Vandahl
• Created: 11/Feb/07 15:25
• Updated: 30/Jul/11 21:51
• Resolved: 05/Apr/07 17:39

Description

The Fulcrum Security-API provides the classes

• org.apache.fulcrum.security.model.basic.entity.BasicGroup
• org.apache.fulcrum.security.model.basic.entity.BasicUser
• org.apache.fulcrum.security.model.dynamic.entity.DynamicGroup
• org.apache.fulcrum.security.model.dynamic.entity.DynamicPermission
• org.apache.fulcrum.security.model.dynamic.entity.DynamicRole
• org.apache.fulcrum.security.model.dynamic.entity.DynamicUser
• org.apache.fulcrum.security.model.turbine.entity.TurbineGroup
• org.apache.fulcrum.security.model.turbine.entity.TurbinePermission
• org.apache.fulcrum.security.model.turbine.entity.TurbineRole
• org.apache.fulcrum.security.model.turbine.entity.TurbineUser
• org.apache.fulcrum.security.model.turbine.entity.TurbineUserGroupRole

The mapping of these classes to new features requires these classes to be extended which is not always desirable, sometimes not even possible. However the classes are used all over the API and particularly in the unit tests. It would be easier to have them as interfaces and provide an additional default implementation for the services that use them now.