You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@struts.apache.org by lu...@apache.org on 2017/04/02 09:13:08 UTC
[07/13] struts-site git commit: cleaned up debugging-struts page
cleaned up debugging-struts 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/a4163950
Tree: http://git-wip-us.apache.org/repos/asf/struts-site/tree/a4163950
Diff: http://git-wip-us.apache.org/repos/asf/struts-site/diff/a4163950
Branch: refs/heads/master
Commit: a4163950514267543f092ba6ea065bea54749554
Parents: e6a5ffd
Author: Stefaan Dutry <st...@gmail.com>
Authored: Sat Apr 1 21:22:05 2017 +0200
Committer: Stefaan Dutry <st...@gmail.com>
Committed: Sat Apr 1 21:22:05 2017 +0200
----------------------------------------------------------------------
source/getting-started/debugging-struts.md | 23 ++++++-----------------
1 file changed, 6 insertions(+), 17 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/struts-site/blob/a4163950/source/getting-started/debugging-struts.md
----------------------------------------------------------------------
diff --git a/source/getting-started/debugging-struts.md b/source/getting-started/debugging-struts.md
index df3d03f..9c38375 100644
--- a/source/getting-started/debugging-struts.md
+++ b/source/getting-started/debugging-struts.md
@@ -10,11 +10,7 @@ __Introduction__
During development of a Struts 2 web application you may want to view the information being managed by the Struts 2 framework. This tutorial will cover two tools you can use to see how Struts 2 views your web application. One tool is the Struts 2 configuration plugin and the other is the debugging interceptor. This article also discusses how to set the log level to see more or fewer log messages.
-
-
-| The Struts 2 [user mailing list](http://struts.apache.org/mail.html)^[http://struts.apache.org/mail.html] is an excellent place to get help. If you are having a problem getting the tutorial example applications to work search the Struts 2 mailing list. If you don't find an answer to your problem, post a question on the mailing list.
-
-|
+The Struts 2 [user mailing list](http://struts.apache.org/mail.html) is an excellent place to get help. If you are having a problem getting the tutorial example applications to work search the Struts 2 mailing list. If you don't find an answer to your problem, post a question on the mailing list.
__Configuration Plugin__
@@ -22,11 +18,9 @@ The Struts 2 config browser plugin provides details about the configuration the
To use the plugin in your application, just call index.action in namespace config-browser. For example you could have the following link on your admin page (or just anywhere during your development).
-
-~~~~~~~
+```html
<a href="<s:url action="index" namespace="config-browser" />">Launch the configuration browser</a>
-
-~~~~~~~
+```
In the example application, there is a link to the configuration browser on the index.jsp page.
@@ -44,14 +38,9 @@ On the left side of the page is the config browser plugin menu. Clicking on cons
__Using the Debugging Interceptor__
-If you have set
-
-~~~~~~~
-devMode
-~~~~~~~
- to true (in the example application see struts.xml) then one of the interceptors that is activated when Struts 2 processes an action is the DebuggingInterceptor. The DebuggingInterceptor looks for a query string appended to the action URL with a name of debug and a value of xml, console, command, or browser.
+If you have set `devMode` to true (in the example application see `struts.xml`) then one of the interceptors that is activated when Struts 2 processes an action is the DebuggingInterceptor. The DebuggingInterceptor looks for a query string appended to the action URL with a name of debug and a value of xml, console, command, or browser.
-If the DebuggingInterceptor finds that query string then it will halt further execution of the action and instead return to the browser debugging information. The format of the returned information depends on the value of the debug query parameter. See _DebuggingInterceptor_ for more detail.
+If the DebuggingInterceptor finds that query string then it will halt further execution of the action and instead return to the browser debugging information. The format of the returned information depends on the value of the debug query parameter. See [DebuggingInterceptor](//struts.apache.org/docs/debugginginterceptor.html) for more detail.
In the example application on the index.jsp is a link for displaying debugging information. This link includes the query string debug=browser. If you click on this link you'll see a table with columns that can be expanded and collapsed. The table contains the various objects and their state being managed by the Struts 2 framework.
@@ -61,7 +50,7 @@ Note that to enable the correct display and interaction of the expand/collapse l
__Struts 2 Logging__
-The Struts 2 framework will write to a log a great deal of information if you've configured the log properties to log at the debug level. In the example application, view log4j.xml. The two major packages involved in the Struts 2 framework, com.opensymphony and org.apache.struts2, are configured to write debug and above log messages. When you run the application view the standard out for your Servlet container to see all the information written to the log. Please check _Logging_ page for other options.
+The Struts 2 framework will write to a log a great deal of information if you've configured the log properties to log at the debug level. In the example application, view `log4j.xml`. The two major packages involved in the Struts 2 framework, `com.opensymphony` and `org.apache.struts2`, are configured to write debug and above log messages. When you run the application view the standard out for your Servlet container to see all the information written to the log. Please check [Logging](//struts.apache.org/docs/logging.html) page for other options.
__Summary__