Configuration Reference - Stripes...and Java Web Development is Fun Again - page 366

Validation.InvokeValidateWhenErrorsExist
This flag indicates whether to continue executing validation methods
when previous validations have produced errors. The default is false .
Here's an example:

<init-param>
<param-name> Validation.InvokeValidateWhenErrorsExist </param-name>
<param-value> true </param-value>
</init-param>

A.4 Interceptors

Stripes automatically loads core interceptors. Moreover, all autodiscov-
ered interceptors are also loaded, but in an unpredictable order. You
can change these defaults with the parameters in this section.

CoreInterceptor.Classes
These are the Interceptor implementations to be automatically loaded
before any other interceptors. The defaults are BeforeAfterMethodInter-
ceptor (required to support @Before and @After ), and HttpCacheIntercep-
tor (required to support @HttpCache ). For example, if you wanted to
replace HttpCacheInterceptor with your own implementation, you could
use this:

<init-param>
<param-name> CoreInterceptor.Classes </param-name>
<param-value>
net.sourceforge.stripes.controller.BeforeAfterMethodInterceptor,
stripesbook.nonext.MyHttpCacheInterceptor
</param-value>
</init-param>

Interceptor.Classes
This is a comma-separated list of Interceptor implementations. Intercep-
tors will be executed in the order that you list them, unlike extension-
packaged interceptors for which the order is not guaranteed. For exam-
ple, if it's important to execute Interceptor1 before Interceptor2 , you would
use this:

<init-param>
<param-name> Interceptor.Classes </param-name>
<param-value>
stripesbook.nonext.Interceptor1,
stripesbook.nonext.Interceptor2
</param-value>
</init-param>