Home >> All >> org >> mentawai

Page 1   2  

•	org.mentawai.message.* (8)	•	org.mentawai.rule.* (11)	•	org.mentawai.tag.* (46)
•	org.mentawai.transaction.* (3)	•	org.mentawai.util.* (4)	•	org.mentawai.velocity.* (2)

Package Samples:

• org.mentawai.velocity
• org.mentawai.util
• org.mentawai.transaction
• org.mentawai.tag.velocity
• org.mentawai.tag.util
• org.mentawai.tag.paginator
• org.mentawai.tag.message
• org.mentawai.tag.i18n
• org.mentawai.tag.html
• org.mentawai.tag.authorization
• org.mentawai.tag.authentication
• org.mentawai.tag
• org.mentawai.rule
• org.mentawai.message

Classes:

• MockAction: A mock for facilitating action testing. It internally creates mocks for the input, output, session and context. Example: Testing the without this mock: MyAction action = new MyAction(); Input input = new InputMap(); Output output = new OutputMap(); Context session = new ContextMap(); Context application = new ContextMap(); action.setInput(input); action.setOutput(output); action.setSession(session); action.setApplication(application); input.setValue("asdasdas", someValue)/ String result = action.execute(); assertEqual(result, "balblablablal"); assertEqual(output.getValue("asdasd"),asdasdasdasdas); ...
• SingleInstanceActionConfig: Use this action config if you want your action to be a single instance for all requests, in other words, you don't want to create a new instance of your action for every request. If you use this action config, it is your responsibility to make your action thread-safe. If you are not sure that your action is thread-safe, than you should not use this action config. Sometimes our actions are so simple (Ex: org.mentawai.action.SuccessAction) that it doesn't make sense to create a new instance for every request. Although this is not a requirement, it is strongly recommended that you use SingleInstanceActionConfigs ...
• HtmlEmail: An HTML multipart email. This class is used to send HTML formatted email. A text message can also be set for HTML unaware email clients, such as text-based email clients. This class also inherits from MultiPartEmail, so it is easy to add attachents to the email. To send an email in HTML, one should create a HtmlEmail, then use the setFrom, addTo, etc. methods. The HTML content can be set with the setHtmlMsg method. The alternate text content can be set with setTextMsg. Either the text or HTML can be omitted, in which case the "main" part of the multipart becomes whichever is supplied rather than ...
• SingleInstanceBaseAction: This is the base class for single instance actions, in other words, those actions that will be instantiated only once and shared among all requests. Sometimes, when you looking for every performance drop, you may not want to create a new action instance for every request. This class keeps the action data in thread locals, so that each thread has its own input, output, session, application and locale. The actions extending this class must be configurated with a SingleInstanceActionConfig. It is your responsibility to make your action thread-safe, otherwise you should stick with the BaseAction class ...
• Action: Describes a Mentawai action, the central idea of the framework architecture. An action has an input (org.mentawai.core.Input) and an output (org.mentawai.core.Output). An action generates a result (java.lang.String) after it is executed. The result is usually SUCCESS or ERROR. For each result there is a consequence (org.mentawai.core.Consequence). The consequences for a web application are usually FORWARD or REDIRECT. An action has access to contexts (org.mentawai.core.Context). The contexts for a web application are usually a SessionContext or a ApplicationContext.
• RedirectAfterLogin: A marker interface to indicate that an action can receive a redirection after a login. An action should implement this interface if it wants to receive a redirection after the user logs in. Redirect After Login is basically this: The user tries to access action /MyAction.mtw The user is not logged, so he is taken to the login page. After a successful login, instead of going to the first page (welcome page), it is taken to the /MyAction.mtw action. For this to happen, MyAction has to implement this marker interface.
• OutputFilter: A filter that takes all the properties of the action and place them in the output, so that you don't have to call output.setValue() manually. Note that this filter uses the method action.getClass().getDeclaredMethods() in order to find the getters, in other words, it will only find getters of the base class and not from its superclasses. This is ok because action inheritance is not very common. For ModelDriven actions, the method action.getModel().getClass().getMethods() is used instead, pretty much like in the OVFilter.
• OVFilter: A filter that takes all the properties of a bean and place them in the action output. Use this filter, for example, if you want to show all properties of an User bean, but you don't want to manually place them in the action output, in other words, you place the User bean in the output and use the OVFilter to accomplish the same result. Note that this filter uses the method Class.getMethods() in order to find the getters, in other words, getters from the class and its superclasses will be called for properties.
• InjectionFilter: A filter that tries to inject the input values in the action through setters. (Ex. setUsername() , setPassword() , etc.) It can also inject the input value directly in the attribute, even if it is a private field. Use this filter if you don't want to deal with the action input object and instaed you want to inject its values in the action. This filter tries to inject all the input values in the action.
• ApplicationManager: The central abstract base manager which controls actions, filters, locales and data lists. You can use this class to register actions and filters through the loadActions() method. You can use this class to specify supported locales through the loadLocales() method. You can use this class to manage the data list loading process. You can use this class to initialize anything for your web application.
• ValidationFilter: A filter to validate the values of an action input. Apply this filter to validate the input values of your actions. By default, error messages are inside the /validation/ directory and a ClassMessageContext is used. (Only if LocaleManager.isUseMasterForEverything returns false) By default, the result returned when the validation fails is BaseAction.ERROR .
• StreamConsequence: A web-based consequence that gets a ready-to-use input stream from the output of the action, get the contents from that input stream and flush them to the servlet output stream. Very useful for loading images from a database, downloads and other resources that the programmer may want to protect from direct access from the client. This class is thread-safe .
• VOFilter: A filter that tries to populate a bean with the action input values. Use this filter if you want to provide your action with a ready-to-use bean instead of a bunch of action input values. This filter tries to inject all the action input values in a Java object through setters. It can also inject directly in the bean's attributes, even if the field is private.
• OutputResponse: A simple Output implementation backed up by a java.util.HashMap. This class also implements the java.util.Map interface so it can be used with JSP Expression Language. This class wraps the HttpServletResponse but does not use it. You may access it through the getResponse() method. Most of map operations are not supported.
• DBCPConnectionHandler: A connection handler that uses the Commons DBCP connection pool. (http://jakarta.apache.org/commons/dbcp/) To use this class you must have the DBCP jars in your /WEB-INF/lib directory. You may access the underlying DBCP's BasicDataSource to configure the pool, before you start calling getConnection().
• C3P0ConnectionHandler: A connection handler that uses the C3P0 connection pool. (http://sourceforge.net/projects/c3p0) To use this class you must have the C3P0 jar in your /WEB-INF/lib directory. You may access the underlying C3P0's ComboPooledDataSource to configure the pool, before you start calling getConnection().
• Input: Defines the behavior of an action input. An Input has parameters and headers. Parameters can be any java object, and not only strings. Headers can be only strings. Parameters are not read-only, and actions and filters can modify it, if they need to. Headers are read-only.
• MultiPartEmail: A multipart email. This class is used to send multi-part internet email like messages with attachments. To create a multi-part email, call the default constructor and then you can call setMsg() to set the message and call the different attach() methods.
• TransactionFilter: Use this filter to put your action inside a transaction. You action will be commited or rolledback depending on its result. The default is to commit if and only if your action returns SUCCESS. However you can pass your own results to define a commit.
• ActionConfig: An ActionConfig links together an action implementation, an action name or alias, action results and action consequences. It makes it possible for an action implementation to be re-used in different situations with different names and consequences.
• ConnectionHandler: This interface describes the behaviour of a Mentawai database connection provider. Classes implementing this interface may or may not use an underlying connection pool. This is a transparent way to get a connection to a database with Mentawai.
• BaseLoginAction: This action implements the basic functionality for a Login action. You should override this class to create your Login action. You should also use its static methods for retrieving the session user and for checking if the user is logged.
• InputRequest: Encapsulates a HttpServletRequest as an Input for Mentawai actions. This class also implements the java.util.Map interface so it can be used with JSP Expression Language. Most of map operations are not supported.
• SimpleListData: This class implements the simplest possible data list, with no locales or i18n files. Use this class if you don't want to deal with internationalization and i18n files, in other words, you just want a list.
• Message: Describes the behavior of a text message that can be displayed in web page. A messsage has an ID and a message context from where to get the message as text. Messages are localized and can have tokens.

Home | Contact Us | Privacy Policy | Terms of Service