Cleans up exported page
Project: http://git-wip-us.apache.org/repos/asf/struts-site/repo Commit: http://git-wip-us.apache.org/repos/asf/struts-site/commit/c758d113 Tree: http://git-wip-us.apache.org/repos/asf/struts-site/tree/c758d113 Diff: http://git-wip-us.apache.org/repos/asf/struts-site/diff/c758d113 Branch: refs/heads/master Commit: c758d11388302b85c8ef02897aa055c2650fd769 Parents: e28a4a6 Author: Lukasz Lenart <lukaszlen...@apache.org> Authored: Mon Jul 31 15:32:01 2017 +0200 Committer: Lukasz Lenart <lukaszlen...@apache.org> Committed: Mon Jul 31 15:32:01 2017 +0200 ---------------------------------------------------------------------- .../interceptor-configuration.md | 50 ++++++++------------ 1 file changed, 19 insertions(+), 31 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/struts-site/blob/c758d113/source/core-developers/interceptor-configuration.md ---------------------------------------------------------------------- diff --git a/source/core-developers/interceptor-configuration.md b/source/core-developers/interceptor-configuration.md index 8b202f8..e6a120b 100644 --- a/source/core-developers/interceptor-configuration.md +++ b/source/core-developers/interceptor-configuration.md @@ -5,7 +5,9 @@ title: Interceptor Configuration # Interceptor Configuration -Interceptors allow you to define code to be executed before and/or after the execution of an Action method\. (The "Filter" pattern\.) Interceptors can be a powerful tool when developing applications\. There are many, many use cases for Interceptors, including validation, property population, security, logging, and profiling\. +Interceptors allow you to define code to be executed before and/or after the execution of an Action method. +(The "Filter" pattern.) Interceptors can be a powerful tool when developing applications. There are many, many use cases +for Interceptors, including validation, property population, security, logging, and profiling. | Validation | Examine input for correctness | |------------|-------------------------------| @@ -13,15 +15,16 @@ Interceptors allow you to define code to be executed before and/or after the exe | Logging | Journal details regarding each action | | Profiling | Time action throughput, looking for performance bottlenecks | -Interceptors can be chained together to create an Interceptor "Stack"\. If an action neeeds to check the client's credentials, log the action, and time the action, all of these routines, and more, could be made part of the same Interceptor Stack\. +Interceptors can be chained together to create an Interceptor "Stack". If an action needs to check the client's +credentials, log the action, and time the action, all of these routines, and more, could be made part of the same +Interceptor Stack. -Interceptors are implemented as Java classes, so each Interceptor has a class name\. To make it easier to reference Interceptors, each class can be registered with the framework and given a unique, simpler name\. +Interceptors are implemented as Java classes, so each Interceptor has a class name. To make it easier to reference +Interceptors, each class can be registered with the framework and given a unique, simpler name. **Registering Interceptors** - -~~~~~~~ - +```xml <interceptors> <interceptor name="security" class="com.company.security.SecurityInterceptor"/> <interceptor-stack name="secureStack"> @@ -29,40 +32,25 @@ Interceptors are implemented as Java classes, so each Interceptor has a class na <interceptor-ref name="defaultStack"/> </interceptor-stack> </interceptors> +``` -~~~~~~~ - - (ok) Individual Interceptors and Interceptors Stacks can be "mixed and matched" in any order when defining an Interceptor Stack\. - - (ok) The framework will invoke each Interceptor on the stack **in the order it is defined**\. - -Most applications will define a default Interceptor Stack, such as - +> Individual Interceptors and Interceptors Stacks can be "mixed and matched" in any order when defining an Interceptor Stack. +> The framework will invoke each Interceptor on the stack **in the order it is defined**. -~~~~~~~ -<default-interceptor-ref name="secureStack"/> -~~~~~~~ - -but any action may also define its own local stack\. +Most applications will define a default Interceptor Stack, such as `<default-interceptor-ref name="secureStack"/>` +but any action may also define its own local stack. **A local Interceptor Stack** - -~~~~~~~ - +```xml <action name="VelocityCounter" class="org.apache.struts2.example.counter.SimpleCounter"> <result name="success">...</result> <interceptor-ref name="defaultComponentStack"/> </action> +``` -~~~~~~~ - -The default configuration ( - -~~~~~~~ - -~~~~~~~ -) sets up a default Interceptor Stack that will work well for most applications\. +The default configuration - [struts-default.xml](struts-default-xml.html); sets up a default Interceptor Stack that +will work well for most applications. -(light\-on) For more, see [Interceptors](interceptors.html). \ No newline at end of file +> For more, see [Interceptors](interceptors.html).
