This is an automated email from the ASF dual-hosted git repository.

ggregory pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


The following commit(s) were added to refs/heads/release-2.x by this push:
     new 89e6d46  Make docs easier to read (for me at least).
89e6d46 is described below

commit 89e6d46068a729c64d9b94c559df738ba5b80c06
Author: Gary Gregory <[email protected]>
AuthorDate: Tue Feb 23 15:06:33 2021 -0500

    Make docs easier to read (for me at least).
---
 src/site/xdoc/manual/webapp.xml | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/src/site/xdoc/manual/webapp.xml b/src/site/xdoc/manual/webapp.xml
index 8860d4c..cfea70f 100644
--- a/src/site/xdoc/manual/webapp.xml
+++ b/src/site/xdoc/manual/webapp.xml
@@ -72,9 +72,18 @@
         <p>
           A Servlet 3.0 or newer web application is any 
<code>&lt;web-app&gt;</code> whose <code>version</code>
           attribute has a value of "3.0" or higher. Of course, the application 
must also be running in a compatible
-          web container. Some examples are: Tomcat 7.0 and higher, GlassFish 
3.0 and higher, JBoss 7.0 and higher,
-          Oracle WebLogic 12c and higher, and IBM WebSphere 8.0 and higher.
+          web container.
         </p>
+        <p>
+          Some examples are:
+        </p>
+        <ul>
+          <li>Tomcat 7.0 and higher</li>
+          <li>GlassFish 3.0 and higher</li>
+          <li>JBoss 7.0 and higher</li>
+          <li>Oracle WebLogic 12c and higher</li>
+          <li>IBM WebSphere 8.0 and higher</li>
+        </ul>
         <h4>The Short Story</h4>
         <p>
           Log4j 2 "just works" in Servlet 3.0 and newer web applications. It 
is capable of automatically starting when
@@ -440,9 +449,9 @@ public class TestAsyncServlet extends HttpServlet {
 
 </Configuration>]]></pre>
         <p>
-          To avoid double logging of exceptions to the servlet context, you 
must use <code>%ex{none}</code> in your 
-          <code>PatternLayout</code> as shown in the example. The exception 
will be omitted from the message text but 
-          it is passed to the servlet context as the actual Throwable object. 
+          To avoid double logging of exceptions to the servlet context, you 
must use <code>%ex{none}</code> in your
+          <code>PatternLayout</code> as shown in the example. The exception 
will be omitted from the message text but
+          it is passed to the servlet context as the actual Throwable object.
         </p>
       </subsection>
     </section>

Reply via email to