Author: norman.richards(a)jboss.com Date: 2009-02-12 20:01:54 -0500 (Thu, 12 Feb 2009) New Revision: 10040 Modified: trunk/doc/Seam_Reference_Guide/en-US/Conversations.xml trunk/doc/Seam_Reference_Guide/en-US/Events.xml Log: JBSEAM-3953 Modified: trunk/doc/Seam_Reference_Guide/en-US/Conversations.xml =================================================================== --- trunk/doc/Seam_Reference_Guide/en-US/Conversations.xml 2009-02-13 00:54:47 UTC (rev 10039) +++ trunk/doc/Seam_Reference_Guide/en-US/Conversations.xml 2009-02-13 01:01:54 UTC (rev 10040) @@ -1176,7 +1176,7 @@ HTTP 503 error: </para> - <programlisting role="XML"><![CDATA[ <exception class="org.jboss.seam.ConcurrentRequestTimeoutException" logLevel="trace"> + <programlisting role="XML"><![CDATA[ <exception class="org.jboss.seam.ConcurrentRequestTimeoutException" log-level="trace"> <http-error error-code="503" /> </exception>]]></programlisting> @@ -1195,7 +1195,7 @@ Alternatively you could redirect to an error page: </para> - <programlisting role="XML"><![CDATA[<exception class="org.jboss.seam.ConcurrentRequestTimeoutException" logLevel="trace"> + <programlisting role="XML"><![CDATA[<exception class="org.jboss.seam.ConcurrentRequestTimeoutException" log-level="trace"> <end-conversation/> <redirect view-id="/error.xhtml"> <message>The server is too busy to process your request, please try again later</message> @@ -1275,4 +1275,4 @@ </itemizedlist> </section> </section> -</chapter> \ No newline at end of file +</chapter> Modified: trunk/doc/Seam_Reference_Guide/en-US/Events.xml =================================================================== --- trunk/doc/Seam_Reference_Guide/en-US/Events.xml 2009-02-13 00:54:47 UTC (rev 10039) +++ trunk/doc/Seam_Reference_Guide/en-US/Events.xml 2009-02-13 01:01:54 UTC (rev 10040) @@ -1077,7 +1077,7 @@ 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 attributes <literal>log</literal> - and <literal>logLevel</literal> can be used to control exception logging. By setting + and <literal>log-level</literal> can be used to control exception logging. By setting <literal>log="false"</literal> as per the following example, then no log message will be generated when the specified exception occurs: </para> @@ -1090,19 +1090,19 @@ <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> + (i.e. the exception will be logged). Alternatively, you can specify the <literal>log-level</literal> to control at which log level the exception will be logged: </para> - <programlisting role="XML"><![CDATA[ <exception class="org.jboss.seam.security.NotLoggedInException" logLevel="info"> + <programlisting role="XML"><![CDATA[ <exception class="org.jboss.seam.security.NotLoggedInException" log-level="info"> <redirect view-id="/register.xhtml"> <message severity="warn">You must be a member to use this feature</message> </redirect> </exception>]]></programlisting> <para> - The acceptable values for <literal>logLevel</literal> are: <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 + The acceptable values for <literal>log-level</literal> are: <literal>fatal, error, warn, info, debug</literal> + or <literal>trace</literal>. If the <literal>log-level</literal> is not specified, or if an invalid value is configured, then it will default to <literal>error</literal>. </para>