struts-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lukaszlen...@apache.org
Subject struts-site git commit: Cleans up exported page
Date Mon, 31 Jul 2017 11:59:16 GMT
Repository: struts-site
Updated Branches:
  refs/heads/master 2169c1295 -> d9b02b9cc


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/d9b02b9c
Tree: http://git-wip-us.apache.org/repos/asf/struts-site/tree/d9b02b9c
Diff: http://git-wip-us.apache.org/repos/asf/struts-site/diff/d9b02b9c

Branch: refs/heads/master
Commit: d9b02b9ccbd1fb683703acc64f6c6c440ed92ce4
Parents: 2169c12
Author: Lukasz Lenart <lukaszlenart@apache.org>
Authored: Mon Jul 31 13:59:02 2017 +0200
Committer: Lukasz Lenart <lukaszlenart@apache.org>
Committed: Mon Jul 31 13:59:02 2017 +0200

----------------------------------------------------------------------
 .../core-developers/exceptio-configuration.md   | 190 -------------------
 .../core-developers/exception-configuration.md  | 130 +++++++++++++
 source/core-developers/index.md                 |   2 +-
 3 files changed, 131 insertions(+), 191 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/struts-site/blob/d9b02b9c/source/core-developers/exceptio-configuration.md
----------------------------------------------------------------------
diff --git a/source/core-developers/exceptio-configuration.md b/source/core-developers/exceptio-configuration.md
deleted file mode 100644
index b98b1be..0000000
--- a/source/core-developers/exceptio-configuration.md
+++ /dev/null
@@ -1,190 +0,0 @@
----
-layout: core-developers
-title: Exception Configuration
----
-
-# Exception Configuration
-
-Exception mappings is a powerful feature for dealing with an Action class that throws an
Exception\. The core idea is that an Exception thrown during the Action method can be automatically
caught and mapped to a predefined Result\. This declarative strategy is especially useful
for frameworks, like Hibernate and Acegi, that throw RuntimeExceptions\.
-
-As with many other parts of the framework, an Interceptor is needed to activate the exception
mapping functionality\. Below is a snippet from 
-
-~~~~~~~
-struts-default.xml
-~~~~~~~
- which has the exception mapping already activated\.
-
-**snippet of struts\-default\.xml**
-
-
-~~~~~~~
-
-...
-<interceptors>
-    ...
-    <interceptor name="exception" class="com.opensymphony.xwork.interceptor.ExceptionMappingInterceptor"/>
-    ...
-</interceptors>
-
-<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="debugging"/>
-    <interceptor-ref name="profiling"/>
-    <interceptor-ref name="scoped-model-driven"/>
-    <interceptor-ref name="model-driven"/>
-    <interceptor-ref name="fileUpload"/>
-    <interceptor-ref name="checkbox"/>
-    <interceptor-ref name="static-params"/>
-    <interceptor-ref name="params"/>
-    <interceptor-ref name="conversionError"/>
-    <interceptor-ref name="validation">
-        <param name="excludeMethods">input,back,cancel,browse</param>
-    </interceptor-ref>
-    <interceptor-ref name="workflow">
-        <param name="excludeMethods">input,back,cancel,browse</param>
-    </interceptor-ref>
-</interceptor-stack>
-...
-
-~~~~~~~
-
-To use exception mapping, we simply need to map Exceptions to specific Results\. The framework
provides two ways to declare an exception mapping 
-
-~~~~~~~
-<exception-mapping/>
-~~~~~~~
- \- globally or for a specific action mapping\. The exception mapping element takes two attributes,

-
-~~~~~~~
-exception
-~~~~~~~
- and 
-
-~~~~~~~
-result
-~~~~~~~
-\.
-
-When declaring an exception mapping, the Interceptor will find the closest class inheritance
match between the Exception thrown and the Exception declared\. The Interceptor will examine
all declared mappings applicable to the action mapping, first local and then global mappings\.
If a match is found, the Result is processed, just as if it had been returned by the Action\.
-
-(information) This process follows the same rules as a Result returned from an Action\. It
first looks for the Result in the local action mapping, and if not found, it looks for a global
Result\.
-
-Below is an example of global and local exception mappings\.
-
-**snippet from struts\.xml**
-
-
-~~~~~~~
-
-<struts>
-    <package name="default">
-        ...
-        <global-results>
-            <result name="login" type="redirect">/Login.action</result>
-            <result name="Exception">/Exception.jsp</result>
-        </global-results>
-
-        <global-exception-mappings>
-            <exception-mapping exception="java.sql.SQLException" result="SQLException"/>
-            <exception-mapping exception="java.lang.Exception" result="Exception"/>
-        </global-exception-mappings>
-        ...
-        <action name="DataAccess" class="com.company.DataAccess">
-            <exception-mapping exception="com.company.SecurityException" result="login"/>
-            <result name="SQLException" type="chain">SQLExceptionAction</result>
-            <result>/DataAccess.jsp</result>
-        </action>
-        ...
-    </package>
-</xwork>
-
-~~~~~~~
-
-In the example above, here is what happens based upon each Exception:
-
-+ A 
-
-~~~~~~~
-java.sql.SQLException
-~~~~~~~
- will chain to the 
-
-~~~~~~~
-SQLExceptionAction
-~~~~~~~
- (action mapping not shown)
-
-+ A 
-
-~~~~~~~
-com.company.SecurityException
-~~~~~~~
- will redirect to 
-
-~~~~~~~
-Login.action
-~~~~~~~
-
-+ Any other exception that extends 
-
-~~~~~~~
-java.lang.Exception
-~~~~~~~
- will return the 
-
-~~~~~~~
-/Exception.jsp
-~~~~~~~
- page
-
-#####Exception Values on the ValueStack#####
-
-By default, the 
-
-~~~~~~~
-ExceptionMappingInterceptor
-~~~~~~~
- adds the following values to the Value Stack:
-
-| exception | The exception object itself |
-|-----------|-----------------------------|
-| exceptionStack | The value from the stack trace |
-
-**Sample JSP using Error and Exception Values**
-
-
-~~~~~~~
- 
-<h2>An unexpected error has occurred</h2>
-<p>
-    Please report this error to your system administrator
-    or appropriate technical support personnel.
-    Thank you for your cooperation.
-</p>
-<hr/>
-<h3>Error Message</h3>
-<s:actionerror/>
-<p>
-    <s:property value="%{exception.message}"/>
-</p>
-<hr/>
-<h3>Technical Details</h3>
-<p>
-    <s:property value="%{exceptionStack}"/>
-</p>
-
-~~~~~~~
-
-#####Exception in constructors#####
-
-Global exception mappings are designed to be used with exceptions thrown by action methods
(like 
-
-~~~~~~~
-execute
-~~~~~~~
-)\. exceptions thrown from constructors will **not** be handled by global exception mappings\.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/struts-site/blob/d9b02b9c/source/core-developers/exception-configuration.md
----------------------------------------------------------------------
diff --git a/source/core-developers/exception-configuration.md b/source/core-developers/exception-configuration.md
new file mode 100644
index 0000000..1cd6e13
--- /dev/null
+++ b/source/core-developers/exception-configuration.md
@@ -0,0 +1,130 @@
+---
+layout: core-developers
+title: Exception Configuration
+---
+
+# Exception Configuration
+
+Exception mappings is a powerful feature for dealing with an Action class that throws an
Exception. The core idea is 
+that an Exception thrown during the Action method can be automatically caught and mapped
to a predefined Result. This 
+declarative strategy is especially useful for frameworks, like Hibernate and Acegi, that
throw RuntimeExceptions.
+
+As with many other parts of the framework, an Interceptor is needed to activate the exception
mapping functionality. 
+Below is a snippet from `struts-default.xml` which has the exception mapping already activated.
+
+**snippet of struts-default.xml**
+
+```xml
+...
+<interceptors>
+    ...
+    <interceptor name="exception" class="com.opensymphony.xwork.interceptor.ExceptionMappingInterceptor"/>
+    ...
+</interceptors>
+
+<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="debugging"/>
+    <interceptor-ref name="profiling"/>
+    <interceptor-ref name="scoped-model-driven"/>
+    <interceptor-ref name="model-driven"/>
+    <interceptor-ref name="fileUpload"/>
+    <interceptor-ref name="checkbox"/>
+    <interceptor-ref name="static-params"/>
+    <interceptor-ref name="params"/>
+    <interceptor-ref name="conversionError"/>
+    <interceptor-ref name="validation">
+        <param name="excludeMethods">input,back,cancel,browse</param>
+    </interceptor-ref>
+    <interceptor-ref name="workflow">
+        <param name="excludeMethods">input,back,cancel,browse</param>
+    </interceptor-ref>
+</interceptor-stack>
+...
+```
+
+To use exception mapping, we simply need to map Exceptions to specific Results. The framework
provides two ways 
+to declare an exception mapping `<exception-mapping/>` - globally or for a specific
action mapping. The exception 
+mapping element takes two attributes, `exception` and `result`.
+
+When declaring an exception mapping, the Interceptor will find the closest class inheritance
match between the Exception 
+thrown and the Exception declared. The Interceptor will examine all declared mappings applicable
to the action mapping, 
+first local and then global mappings. If a match is found, the Result is processed, just
as if it had been returned 
+by the Action.
+
+> This process follows the same rules as a Result returned from an Action. It first looks
for the Result in the local 
+> action mapping, and if not found, it looks for a global Result.
+
+Below is an example of global and local exception mappings.
+
+**snippet from struts.xml**
+
+```xml
+<struts>
+    <package name="default">
+        ...
+        <global-results>
+            <result name="login" type="redirect">/Login.action</result>
+            <result name="Exception">/Exception.jsp</result>
+        </global-results>
+
+        <global-exception-mappings>
+            <exception-mapping exception="java.sql.SQLException" result="SQLException"/>
+            <exception-mapping exception="java.lang.Exception" result="Exception"/>
+        </global-exception-mappings>
+        ...
+        <action name="DataAccess" class="com.company.DataAccess">
+            <exception-mapping exception="com.company.SecurityException" result="login"/>
+            <result name="SQLException" type="chain">SQLExceptionAction</result>
+            <result>/DataAccess.jsp</result>
+        </action>
+        ...
+    </package>
+</xwork>
+```
+
+In the example above, here is what happens based upon each Exception:
+
+- A `java.sql.SQLException` will chain to the `SQLExceptionAction` (action mapping not shown)
+- A `com.company.SecurityException` will redirect to `Login.action`
+- Any other exception that extends `java.lang.Exception` will return the `/Exception.jsp`
page
+
+## Exception Values on the ValueStack
+
+By default, the `ExceptionMappingInterceptor` adds the following values to the Value Stack:
+
+| exception | The exception object itself |
+|-----------|-----------------------------|
+| exceptionStack | The value from the stack trace |
+
+**Sample JSP using Error and Exception Values**
+
+```jsp 
+<h2>An unexpected error has occurred</h2>
+<p>
+    Please report this error to your system administrator
+    or appropriate technical support personnel.
+    Thank you for your cooperation.
+</p>
+<hr/>
+<h3>Error Message</h3>
+<s:actionerror/>
+<p>
+    <s:property value="%{exception.message}"/>
+</p>
+<hr/>
+<h3>Technical Details</h3>
+<p>
+    <s:property value="%{exceptionStack}"/>
+</p>
+```
+
+## Exception in constructors
+
+Global exception mappings are designed to be used with exceptions thrown by action methods
(like `execute`). exceptions 
+thrown from constructors will **not** be handled by global exception mappings.

http://git-wip-us.apache.org/repos/asf/struts-site/blob/d9b02b9c/source/core-developers/index.md
----------------------------------------------------------------------
diff --git a/source/core-developers/index.md b/source/core-developers/index.md
index df58ef6..3fad4ae 100644
--- a/source/core-developers/index.md
+++ b/source/core-developers/index.md
@@ -22,7 +22,7 @@ Each may be configured via XML or annotations.
 - [Annotations](annotations.html)
 - [Configuration Elements](configuration-elements.html)
   - [Actions](action-configuration.html), [Wildcard Mappings](wildcard-mappings.html), [Beans](bean-configuration.html),
[Constants](constant-configuration.html)
-  - [Exceptions](exceptio-configuration.html), [Includes](include-configuration.html), [Interceptors](interceptor-configuration.html)
+  - [Exceptions](exception-configuration.html), [Includes](include-configuration.html), [Interceptors](interceptor-configuration.html)
   - [Namespaces](namespace-configuration.html), [Packages](package-configuration.html), [Results](result-configuration.html)
   - [Unknown Handlers](unknown-handlers.html), [Dispatcher](dispatcher.html)
 - [Configuration Files](configuration-files.html)


Mime
View raw message