From seam-commits at lists.jboss.org Wed Jan 30 05:58:20 2008
Content-Type: multipart/mixed; boundary="===============4625505723329594259=="
MIME-Version: 1.0
From: seam-commits at lists.jboss.org
To: seam-commits at lists.jboss.org
Subject: [seam-commits] Seam SVN:  r7305 - trunk/doc/reference/en/modules.
Date: Wed, 30 Jan 2008 05:58:20 -0500
Message-ID: <E1JKAe4-0001Nh-LU@committer01.frg.pub.inap.atl.jboss.com>

--===============4625505723329594259==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: shane.bryzak(a)jboss.com
Date: 2008-01-30 05:58:20 -0500 (Wed, 30 Jan 2008)
New Revision: 7305

Modified:
   trunk/doc/reference/en/modules/events.xml
Log:
JBSEAM-2071

Modified: trunk/doc/reference/en/modules/events.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/doc/reference/en/modules/events.xml	2008-01-30 10:52:55 UTC (rev =
7304)
+++ trunk/doc/reference/en/modules/events.xml	2008-01-30 10:58:20 UTC (rev =
7305)
@@ -985,7 +985,45 @@
            was actually handled by an exception handler. The outermost (wr=
apper) exception is =

            also available, as <literal>org.jboss.seam.exception</literal>.
          </para>
+         =

+         <sect3>
+             <title>Suppressing exception logging</title>
+             =

+             <para>
+                 For the exception handlers defined in <literal>pages.xml<=
/literal>, it is possible
+                 to declare the logging level at which the exception will =
be logged, or to even
+                 suppress the exception being logged altogether.  The attr=
ibutes <literal>log</literal>
+                 and <literal>logLevel</literal> can be used to control ex=
ception logging.  By setting =

+                 <literal>log=3D"false"</literal> as per the following exa=
mple, then no log message will
+                 be generated when the specified exception occurs:
+             </para>
+             =

+             <programlisting><![CDATA[    <exception class=3D"org.jboss.se=
am.security.NotLoggedInException" log=3D"false">
+        <redirect view-id=3D"/register.xhtml">
+            <message severity=3D"warn">You must be a member to use this fe=
ature</message>
+        </redirect>
+    </exception>]]></programlisting>
+    =

+             <para>
+                 If the <literal>log</literal> attribute is not specified,=
 then it defaults to <literal>true</literal>
+                 (i.e. the exception will be logged).  Alternatively, you =
can specify the <literal>logLevel</literal>
+                 to control at which log level the exception will be logge=
d:             =

+             </para>
 =

+             <programlisting><![CDATA[    <exception class=3D"org.jboss.se=
am.security.NotLoggedInException" logLevel=3D"info">
+        <redirect view-id=3D"/register.xhtml">
+            <message severity=3D"warn">You must be a member to use this fe=
ature</message>
+        </redirect>
+    </exception>]]></programlisting>
+    =

+              <para>
+                  The acceptable values for <literal>logLevel</literal> ar=
e: <literal>fatal, error, warn, info, debug</literal> =

+                  or <literal>trace</literal>.  If the <literal>logLevel</=
literal> is not specified, or if an invalid value is
+                  configured, then it will default to <literal>error</lite=
ral>.              =

+              </para>
+         =

+         </sect3>
+
         </sect2>
         =

         <sect2>


--===============4625505723329594259==--