Dashboard > WebWork > ... > Interceptors > Workflow Interceptor
  WebWork Log In View a printable version of the current page.  
  Workflow Interceptor
Added by Onyeje Bose, last edited by tm_jee on Jun 11, 2006  (view change)
Labels: 
(None)

An interceptor that does some basic validation workflow before allowing the interceptor chain to continue.

This interceptor does nothing if the name of the method being invoked is specified in the excludeMethods parameter. excludeMethods accepts a comma-delimited list of method names. For example, requests to foo!input.action and foo!back.action will be skipped by this interceptor if you set the excludeMethods parameter to "input, back".

The order of execution in the workflow is:

  1. If the action being executed implements Validateable, the action's Validateable#validate() validate method is called.
  2. Next, if the action implements ValidationAware, the action's ValidationAware#hasErrors() hasErrors method is called. If this method returns true, this interceptor stops the chain from continuing and immediately returns Action#INPUT

Note: if the action doesn't implement either interface, this interceptor effectively does nothing. This interceptor is often used with the validation interceptor. However, it does not have to be, especially if you wish to write all your validation rules by hand in the validate() method rather than in XML files.

NOTE: As this method extends off MethodFilterInterceptor, it is capable of deciding if it is applicable only to selective methods in the action class. See MethodFilterInterceptor for more info.

Update: Added logic to execute a validate{MethodName} rather than a general validate method. This allows us to run some validation logic based on the method name we specify in the ActionProxy. For example, you can specify a validateInput() method, or even a validateDoInput() method that will be run before the invocation of the input method.

In DefaultWorkflowInterceptor

applies only when action implements com.opensymphony.xwork.Validateable

  1. if the action class have validate{MethodName}(), it will be invoked
  2. else if the action class have validateDo{MethodName}(), it will be invoked
  3. no matter if 1] or 2] is performed, if alwaysInvokeValidate property of the interceptor is "true" (which is by default "true"), validate() will be invoked.

Parameters

  • alwaysInvokeValidate - Default to true. If true validate() method will always be invoked, otherwise it will not.

Extending the Interceptor

There are no known extension points for this interceptor.

Examples

<action name="someAction" class="com.examples.SomeAction">
    <interceptor-ref name="params"/>
    <interceptor-ref name="validation"/>
    <interceptor-ref name="workflow"/>
    <result name="success">good_result.ftl</result>
</action>

<-- In this case myMethod of the action class will not pass through 
       the workflow process -->
<action name="someAction" class="com.examples.SomeAction">
    <interceptor-ref name="params"/>
    <interceptor-ref name="validation"/>
    <interceptor-ref name="workflow">
        <param name="excludeMethods">myMethod</param>
    </interceptor-ref name="workflow">
    <result name="success">good_result.ftl</result>
</action>

Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request - Contact Administrators