The docs say
> otherwise, the application will fail to start with an exception. 

Is this true? Or should that be ...logging will fail to start with an 
exception. 

Sent from my iPhone

> On 2014/09/22, at 8:09, [email protected] wrote:
> 
> Doc update regarding how servlet contexts can be named.
> 
> 
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/3c868456
> Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/3c868456
> Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/3c868456
> 
> Branch: refs/heads/master
> Commit: 3c868456ed043673a889cdcd0afe3513a695dd72
> Parents: 0e5cc42
> Author: Matt Sicker <[email protected]>
> Authored: Sun Sep 21 17:21:07 2014 -0500
> Committer: Matt Sicker <[email protected]>
> Committed: Sun Sep 21 17:21:07 2014 -0500
> 
> ----------------------------------------------------------------------
> src/site/xdoc/manual/webapp.xml | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
> ----------------------------------------------------------------------
> 
> 
> http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/3c868456/src/site/xdoc/manual/webapp.xml
> ----------------------------------------------------------------------
> diff --git a/src/site/xdoc/manual/webapp.xml b/src/site/xdoc/manual/webapp.xml
> index ecad1f9..1b86d45 100644
> --- a/src/site/xdoc/manual/webapp.xml
> +++ b/src/site/xdoc/manual/webapp.xml
> @@ -177,17 +177,19 @@
>       <subsection name="Context Parameters">
>         <a name="ContextParams" />
>         <p>
> -          By default, Log4j 2 uses the <code>ServletContext</code>'s context 
> name as the <code>LoggerContext</code> name
> -          and uses the standard pattern for locating the Log4j configuration 
> file. There are three context parameters
> -          that you can use to control this behavior. The first, 
> <code>isLog4jContextSelectorNamed</code>, specifies
> -          whether the context should be selected using the
> +          By default, Log4j 2 uses the <code>ServletContext</code>'s
> +          <a 
> href="http://docs.oracle.com/javaee/6/api/javax/servlet/ServletContext.html#getServletContextName()">context
>  name</a>
> +          as the <code>LoggerContext</code> name and uses the standard 
> pattern for locating the Log4j configuration
> +          file. There are three context parameters that you can use to 
> control this behavior. The first,
> +          <code>isLog4jContextSelectorNamed</code>, specifies whether the 
> context should be selected using the
>           <a class="javadoc" 
> href="../log4j-core/apidocs/org/apache/logging/log4j/core/selector/JndiContextSelector.html"
>> JndiContextSelector</a>. If <code>isLog4jContextSelectorNamed</code> is not 
>> specified or is anything other
>           than <code>true</code>, it is assumed to be <code>false</code>.
>         </p>
>         <p>
>           If <code>isLog4jContextSelectorNamed</code> is <code>true</code>, 
> <code>log4jContextName</code> must be
> -          specified; otherwise, the application will fail to start with an 
> exception. <code>log4jConfiguration</code>
> +          specified or <code>display-name</code> must be specified in 
> <code>web.xml</code>; otherwise, the application
> +          will fail to start with an exception. 
> <code>log4jConfiguration</code>
>           <em>should</em> also be specified in this case, and must be a valid 
> URI for the configuration file; however,
>           this parameter is not required.
>         </p>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to