Simplifying the interceptor stack 2007-02-08 - By mraible
Back
I'm working to simplify the stack that I used to use in a WebWork
application. Here's what I currently have:
<interceptors>
<!-- Interceptor to handle allowing only admins to certain
actions -->
<interceptor name="adminOnly" class="adminInterceptor"/>
<!-- https://issues.apache.org/struts/browse/WW-1187 -->
<interceptor-stack name="defaultStack">
<interceptor-ref name="exception"/>
<interceptor-ref name="alias"/>
<interceptor-ref name="servlet-config"/>
<interceptor-ref name="prepare"/>
<interceptor-ref name="i18n"/>
<interceptor-ref name="chain"/>
<interceptor-ref name="model-driven"/>
<interceptor-ref name="fileUpload"/>
<interceptor-ref name="static-params"/>
<interceptor-ref name="params"/>
<interceptor-ref name="conversionError"/>
<interceptor-ref name="validation">
<param
name="excludeMethods">cancel,execute,delete,edit,list,start</param>
</interceptor-ref>
<interceptor-ref name="workflow">
<param name="excludeMethods">input,back,cancel</param>
</interceptor-ref>
</interceptor-stack>
</interceptors>
Is there an easier way to override the validation and workflow methods?
Someone recently pointed out that I don't have the checkbox interceptor in
my stack (which didn't exist in WW).
Is it possible to remove everything but the validation and workflow
interceptors?
Also, are there any performance reasons to have separate stacks for display
only (list) screens vs. forms (crud)?
Thanks,
Matt
--
View this message in context: http://www.nabble.com/-struts-2 (See http://uts-2.ora-code.com)--Simplifying-the
-interceptor-stack-tf3196039.html#a8874246
Sent from the Struts - User mailing list archive at Nabble.com.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)
|
|
