| Home >> All >> org >> javahispano >> canyamo >> [ core Javadoc ] |
• org.javahispano.canyamo.core: Javadoc index of package org.javahispano.canyamo.core.
Package Samples:
• org.javahispano.canyamo.core.action
• org.javahispano.canyamo.core.application
• org.javahispano.canyamo.core.command
• org.javahispano.canyamo.core.config
• org.javahispano.canyamo.core.display
Classes:
• TransparentAction: Empty interface for Actions which should not be registered for "LAST_ACTION" funcionality. Sometimes it's pretty helpfull if after login we can stay in the place we were, so we register the last processed actions. But sometimes this carries an undiserable effect, because some actions should not be registered. A good example is the case "logout -> login". After login we ant to stay in the same place (for example viewing a file, and login to edit it), but if we work always this way, we will never be able to login after a logout, because after login will be logout automatically processed. This interface ...
• Action: Interface that should implement all actions to be managed by Canyamo. An action is a "process" that Canyamo can execute in response to an User request. Actions should manipulated the data in order to satisfied User's request, and put data related to the response in WorkData , which will be passed to the associated Displayer , which would render the response in HTML form.
• Canyamo: Kernel of the Framework This class is the central point of the framework. It receives User's request from Servlet and should be process it correctly. It delegates most of the work to ActionManager and DisplayerManager , which are responsible of get and process the correct action, and render the selected displayer, respectively . This class communicates both of them.
• Application: Maintain all info related to an application. Important ist the property "prefix". Prefix is the text to be write before the item (action or displayer) to used it for example, if prefix is "news", and this application has an Action which name is "add", it should be requested as "news.add.action", the same for displayers "news.show".
• ActionListener: Listener for the execution of Action This interface should be implement for all Displayers which want to know when an Action is executed. Normally this is the case of Displayers that make some kind of caching of content-data, but it can be implement for clases called "commands" that shoul run when an action is executed.
• AbstractAction: Help class that implement almost all methods from Action Only method process is declared abstract, so the extending class are encouregad to implement it and the framework can work fine
• CanyamoLog: Static class that acts as log system for Canyamo. Based in ServletContext's log to write in AppServer's log.
• DisplayerManager: This class manages all displayers present in the system and it is responsible to render the selected one
• Command: Interface to represent "commands" that the framework can run, normally as ActionListener for actions
• FullscreenDisplayer: This interface is a flag to indicate a portlet should be shown alone, without site's enviroment.
• Displayer: Interface to represent "displayers", so the framework can manage all of them the same way
• WorkData: Encapsulates an user's request + response to be used along the framework
• CanyamoMessages: Class that manages all messages from Canyamo (mainly login messages!)
• CanyamoException: Excepcion para indicar errores ocurridos al manipular Portlets
• ActionManager: This (Singleton) class manage all Actions loaded by Canyamo
• CanyamoServlet: Servlet that acts as entry point fro the web application
• AbstractCommand: Description of the Class
• ActionHandler: Description of the Class
• ApplicationHandler: Description of the Class
• CanyamoConfig: Description of the Class
• CanyamoHandler: Description of the Class
• CommandHandler: Description of the Class
• ConfigLoader: Description of the Class
• DisplayerHandler: Description of the Class
| Home | Contact Us | Privacy Policy | Terms of Service |