Home >> All >> org >> apache >> turbine >> modules >> [ actions Javadoc ]

•	org.apache.turbine.modules.actions.sessionvalidator.* (4)

• org.apache.turbine.modules.actions: Javadoc index of package org.apache.turbine.modules.actions.


Package Samples:

• org.apache.turbine.modules.actions.sessionvalidator: Action class implementations.  

Classes:

• AccessController: This action doPerforms an Access Control List and places it into the RunData object, so it is easily available to modules. The ACL is also placed into the session. Modules can null out the ACL to force it to be rebuilt based on more information. Turbine uses a User-Role-Permission arrangement for access control. Users are assigned Roles. Roles are assigned Permissions. Turbine modules then check the Permission required for an action or information with the set of Permissions currently associated with the session (which are dependent on the user associated with the session.) The criteria for assigning ...
• DefaultSessionValidator: The SessionValidator attempts to retrieve the User object from the Servlet API session that is associated with the request. If the data cannot be retrieved, it is handled here. If the user has not been marked as being logged into the system, the user is rejected and the screen is set to the screen.homepage value in TurbineResources.properties. Other systems generally have a database table which stores this information, but we take advantage of the Servlet API here to save a hit to the database for each and every connection that a user makes. This action is special in that it should only be executed ...
• SessionValidator: The SessionValidator attempts to retrive the User object from the Servlet API session that is associated with the request. If the data cannot be retrieved, it is handled here. If the user has not been marked as being logged into the system, the user is rejected and the screen is set to the screen.homepage value in TurbineResources.properties. Other systems generally have a database table which stores this information, but we take advantage of the Servlet API here to save a hit to the database for each and every connection that a user makes. This action is special in that it should only be executed ...
• TemplateSecureSessionValidator: SessionValidator that requires login for use with Template Services like Velocity or WebMacro. Templating services requires a different Session Validator because of the way it handles screens. If you use the WebMacro or Velocity Service with the DefaultSessionValidator, users will be able to bypass login by directly addressing the template using template/index.wm. This is because the Page class looks for the keyword "template" in the Path information and if it finds it will reset the screen using it's lookup mechanism and thereby bypass Login. Note that you will need to set the template.login property ...
• VelocitySecureAction: VelocitySecure action. Always performs a Security Check that you've defined before executing the doBuildtemplate(). You should extend this class and add the specific security check needed. If you have a number of screens that need to perform the same check, you could make a base screen by extending this class and implementing the isAuthorized(). Then each action that needs to perform the same check could extend your base action.
• TemplateSessionValidator: SessionValidator for use with the Template Service, the TemplateSessionValidator is virtually identical to the TemplateSecureValidator except that it does not transfer to the login page when it detects a null user (or a user not logged in). The Template Service requires a different Session Validator because of the way it handles screens. Note that you will need to set the template.login property to the login template.
• LoginUser: This is where we authenticate the user logging into the system against a user in the database. If the user exists in the database that users last login time will be updated.
• VelocityAction: This class provides a convenience methods for Velocity Actions to use. Since this class is abstract, it should only be extended and not used directly.
• JspAction: This class provides a convenience methods for Jsp Actions to use. Since this class is abstract, it should only be extended and not used directly.
• LogoutUser: This action removes a user from the session. It makes sure to save the User object in the session.
• DefaultAction: This is a Default Action module that doesn't do much.
• InitContextsAction: Used to initialize JNDI contexts.

Home | Contact Us | Privacy Policy | Terms of Service