Home >> All >> org >> apache >> turbine >> [ om Javadoc ]

•	org.apache.turbine.om.peer.* (1)	•	org.apache.turbine.om.security.* (18)
•	org.apache.turbine.om.security.peer.* (7)

• org.apache.turbine.om: Javadoc index of package org.apache.turbine.om.


Package Samples:

• org.apache.turbine.om.security.peer: Security object definitions for the Security Service.  
• org.apache.turbine.om.peer
• org.apache.turbine.om.security

Classes:

• TurbineGroup: This class represents a Group of Users in the system that are associated with specific entity or resource. The users belonging to the Group may have various Roles. The Permissions to perform actions upon the resource depend on the Roles in the Group that they are assigned. Certain Roles that the Users may have in the system may are not related to any specific resource nor entity. They are assigned within a special group named 'global' that can be referenced in the code as Group.GLOBAL_GROUP_NAME 55 .
• TurbineUser: A generic implementation of User interface. This basic implementation contains the functionality that is expected to be common among all User implementations. You are welcome to extend this class if you wish to have custom functionality in your user objects (like accessor methods for custom attributes). Note that implementing a different scheme of user data storage normally involves writing an implementation of org.apache.turbine.services.security.UserManager interface.
• BasePeer: This is the base class for all Peer classes in the system. Peer classes are responsible for isolating all of the database access for a specific business object. They execute all of the SQL against the database. Over time this class has grown to include utility methods which ease execution of cross-database queries and the implementation of concrete Peers.
• Group: This class represents a Group of Users in the system that are associated with specific entity or resource. The users belonging to the Group may have various Roles. The Permissions to perform actions upon the resource depend on the Roles in the Group that they are assigned.
• SecurityEntity: This class represents a Group of Users in the system that are associated with specific entity or resource. The users belonging to the Group may have various Roles. The Permissions to perform actions upon the resource depend on the Roles in the Group that they are assigned.
• Permission: This class represents the permissions that a Role has to access certain pages/functions within the system. The class implements Comparable so that when Permissions are added to a Set, they will be in alphabetical order by name.
• TurbinePermission: This class represents the permissions that a Role has to access certain pages/functions within the system. The class implements Comparable so that when Permissions are added to a Set, they will be in alphabetical order by name.
• UserPeer: Peer classes for an User object need to implement this interface. The purpose of this class is to decouple DBSecurityService from the default User implementation and it's related Peer class.
• TurbineUserTest: Test the TurbineUser This tests that we can use the TurbineUser classes. Note, this can be very dependent on various configuration values.
• PermissionPeer: This class handles all the database access for the PERMISSION table. This table contains all the permissions that are used in the system.
• RolePermissionPeer: This class handles all database access for the ROLE_PERMISSION table. This table contains all the permissions for a given role.
• GroupPeer: This class handles all the database access for the Group table. This table contains all the Groups that a given member can play.
• UserGroupRolePeer: This class handles all database access for the VISITOR_ROLE table. This table contains all the roles that a given user can play.
• RolePeer: This class handles all the database access for the ROLE table. This table contains all the roles that a given member can play.
• TurbineUserPeer: This class handles all the database access for the User/User table. This table contains all the information for a given user.
• User: This interface represents functionality that all users of the Turbine system require.
• Role: This class represents a role played by the User associated with the current Session.
• TurbineRole: This class represents a role played by the User associated with the current Session.
• SecurityObject: This class represents a generic object used in the Access Control Lists.
• Retrievable: This interface specifies methods for uniquely identifying an object.
• Retriever: This interface marks a class that has a retrieve(String) method.
• OMTool: A Pull tool to make om objects available to a template
• RetrieverFactory

Home | Contact Us | Privacy Policy | Terms of Service