| Home >> All >> com >> jcorporate >> expresso >> services >> [ controller Javadoc ] |
• com.jcorporate.expresso.services.controller: Javadoc index of package com.jcorporate.expresso.services.controller.
Package Samples:
• com.jcorporate.expresso.services.controller.dbmaint: This package contains Controller objects to perform basic administration functions within Expresso, including security maintenance, testing, and default error handling.
• com.jcorporate.expresso.services.controller.configuration: This package contains Controller objects to perform basic administration functions within Expresso, including security maintenance, testing, and default error handling.
• com.jcorporate.expresso.services.controller.tests
• com.jcorporate.expresso.services.controller.ui
Classes:
• SimpleRegistration: SimpleRegistration Controller. This is the implementation example of Registration. Depends on: Login Controller Email Validator Registration Validator Reg Domain DBObjects Reg Domain DBObject Map The following states are the usual entry points into the registration controller showDBMenu - For users that want to change/edit their registraiton info promptAddRecord - Where we prompt the user to fill out the registration information promptSelfRegister - Where we prompt for login information et.al. from users who wish to self-register promptApproval - For approval administrators only. Shows the registration ...
• DBMaint: Controller that enables basic maintenance (add/update/delete) of any DBObject DBMaint acts more as a controller for allowing operations on DBObjects. The real work for adding, deleting, searching and updating is carried out by a series of classes that are dynamically instantiated and live in the com.jcorporate.expresso.core.servlet.commands package. These classes can be extended to add additional functionality. When tracking down code functionality, the core states are in package: com.jcorporate.expresso.services.dbmaint The only state handlers embedded in the class are minimalistic classes ...
• WizardFormStack: Utility class for wizard type interfaces. Call processNewState() for each 'prompt' state. Ignore for each process state. Typical Usage WizardFormStack.getInstance(request).processNewState(this, request,response); Transition backBtn = WizardFormStack.getInstance(request).getPreviousTransition(); if (backBtn != null) { response.add(backBtn); } The issues with using this class include: (1) The WizardFormStack does not work across multiple controllers. (2) You must not use a parameter named 'back' in your form since this is required to detect if you've gone backwards in the workflow.
• ValidationController: This is an Expresso controller that responds to the validator clicking on an URL provided to him from the notification from the validation job. It has the responsibility of extracting the parameters from the request, resurrecting the Validation entry using the validation-db-context and the validation id. It then compares the code provided in the request with that stored in the validation entry. If the code matches, then the application-supplied validation handler is called to allow the validated-process to go through.
• Registration: Registration Controller. Provides services for self-registering people... ie sign-up pages on websites. This is the abstract class from which all Registration class should extend from. This class contains most of the non prompt/process methods Depends on: Login Controller Email Validator Registration Validator
• EditUserPreference: Allow a user to edit his/her user preferences, optionally restricting to a single set of preferences. Objects that have user preferences defined can call this controller, passing their classname, to allow editing of preferences specific to that object. Calling without specifying a classname allows editing of all of the user's own preferences.
• LoginController: Main Login Controller - used for login/logout and basic interaction with the registration system. This class recognizes the 'registration' classHandler name in the expresso-config.xml It uses the classname in that field to construct and forward to the appropriate registration class. Creation date: (5/12/2001 6:36:41 PM)
• Add: Displays a form for a new DBObject record. This state does not actually perform the adding of the dbobject to the database, instead it creates a blank form that is pre-populated with the default values of the given DBObject. The actual class that does the updating is AddUpdate
• SimpleLoginController: Main Login Controller - used for login/logout and basic interaction with the registration system. This class recognizes the 'registration' classHandler name in the expresso-config.xml It uses the classname in that field to construct and forward to the appropriate registration class.
• ViewBlob: This state allows for viewing of BLOB data types. It supports standard blob types by sending a mime type of application/x-unknown, and is supports MediaDbObjects be setting MIME type, file name, and size to that of the file that was originally uploaded to the database table.
• SearchList: Processes the data passed via a standard form from SEARCH. This class requires a match on all specified fields of a DBObject for a successful outcome. SEARCHsearch can be extended to enabling a more restrictive search on only one or two fields e.g. a foreign key field
• CacheControl: This Controller allows control of the CacheManager. It allows any or all caches to be cleared, and permits the current status of the cache to be displayed. This controller is called when the cache requires and update triggered from a seperate VM.
• DynamicCmd: Base class for all command classes. This class provides the execute() method which all subclasses need to override. IT does some basic functionality that all the DBMaint states need, such as load the given DBObject as specified.
• ShowComponent: State that displays a particular component. The state displays all the properties for the components, provides transitions for all management systems and displays all the inputs for modifying properties of the component.
• RegistrationFactory: Registration factory implements the two required method to deal with Login and registration. Normally Schema implements this interface since it's easy for a controller to get the schema associated with it.
• JobSecurityMatrix: The JobSecurityMatrix controller allows easy administration of the security rights of user groups to get to certain Jobs and to certain methods in those Jobs (assuming the job has more than one method).
• CacheAutoElement: implementation of the AutoController Element which also uses Form Cache to set object values during creation phase. This is appropriate for times when, after an error, user's typing should be preserved
• CronController: Crontab Controller allows for basic insight into the currently running crontabs on the system. It also allows for basic editing and removal of existing crontabs. It does not create new crontabs yet.
• Search: allows the user to search for a record. This class requires a match on all supplied fields of a DBObject. Search can be extended to allow a search on one or more fields e.g. a foreign key field
• UpdateBase: Base Class for posting add, delete and updating operations. This functionality was previously carried out in the DBMaint.doPost(). Now extended by ADDsave, UPDATEsave and UPDATEdelete method.
• AutoControllerElement: This interface is for objects that provide an automatic rendering capability to the system. It's in sort of a way a bridge between DBObjects and ControllerElements
• DBMaintTests: Unit tests some of the states for the DBMaint Controller. This isn't so much of a thorough test as it is a check to make sure states are displaying properly.
• Update: Provides a standard form for user to update all fields (except primary key). Extend this class if only updating one or several but not all fields.
• DBSecurityMatrix: The DBSecurityMatrix controller allows authorized users to easily maintain the security permissions of different user groups to database objects.
• DefaultAutoElement: Default implementation of the AutoController Element. Provides a default unified method for rendering/parsing Inputs from DBObjects
| Home | Contact Us | Privacy Policy | Terms of Service |