...
- timer: clocks how long the action (including nested interceptors and view) takes to execute;
- logger: logs the action being executed;
- chain: makes the previous action's properties available to the current action. Used to make action chaining (reference: Result Types);
- static-params: sets the parameters defined in
xwork.xml
onto the action. These are the<param />
tags that are direct children of the<action />
tag; - params: sets the request (POST and GET) parameters onto the action class. We have seen an example of this in TODO;
- model-driven: if the action implements
ModelDriven
, pushes thegetModel()
result onto the Value Stack; - component: enables and makes registered components available to the actions. (reference: IoC & Components);
- token: checks for valid token presence in action, prevents duplicate form submission;
- token-session: same as above, but storing the submitted data in session when handed an invalid token;
- validation: performs validation using the validators defined in {
Action}-validation.xml
(reference: Validation). We've seen an example of this in lesson 4.1.1; - workflow: calls the validate method in your action class. If action errors created then it returns the
INPUT
view. Good to use together with the validation interceptor (reference: Validation); - servlet-config: give access to
HttpServletRequest
andHttpServletResponse
(think twice before using this since this ties you to the Servlet API); - prepare: allows you to programmatic access to your Action class before the parameters are set on it.;
- conversionError: Adds field errors if any type-conversion errors occurred.
- execAndWait: Spawns a separate thread to execute the action
- fileUpload: Sets uploaded files as action files (File objects)
...