logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject cvs commit: logging-log4j/examples/tiny-webapp INSTALL.txt
Date Wed, 19 Jan 2005 14:11:23 GMT
ceki        2005/01/19 06:11:23

  Modified:    examples/tiny-webapp INSTALL.txt
  Log:
  - small corrections
  - removed the "KNOWN PROBLEMS" section because ContextJNDISelector no longer uses log4j.xml
or log4j.properties as
  default configration file names for non-default repositories. For non-default repositoeies,
the configuration resource must
  be named explicitly.
  
  Revision  Changes    Path
  1.4       +15 -36    logging-log4j/examples/tiny-webapp/INSTALL.txt
  
  Index: INSTALL.txt
  ===================================================================
  RCS file: /home/cvs/logging-log4j/examples/tiny-webapp/INSTALL.txt,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- INSTALL.txt	14 Dec 2004 13:42:14 -0000	1.3
  +++ INSTALL.txt	19 Jan 2005 14:11:23 -0000	1.4
  @@ -16,13 +16,15 @@
     Other Servlet containers such as Jetty also have folders for 
     shared jar files.
   
  -- When launching your java web *server*, make sure to add the
  -  log4j.repositorySelectorClass system property on the java command
  -  line.
  +- On the java command line launching your java web *server*, make sure to 
  +  add te log4j.repositorySelectorClass system property. For the 
  +  JNDIContextSelector the exact system property to add is:
   
  -  For the JNDIContextSelector the exact system property to add is:
  -
  -     -Dlog4j.repositorySelectorClass="JNDI" 
  +     -Dlog4j.repositorySelectorClass=org.apache.log4j.selector.ContextJNDISelector
  +  
  +  or in its equivalent short form
  +  
  +     -Dlog4j.repositorySelectorClass=JNDI 
        
   - You can now run the supplied web-applications hello.war and
     tata.war.
  @@ -69,7 +71,7 @@
   - Specify the URL for this context's configuration resource using 
     the "log4j/configuration-resource" environment entry.
     The repository selector (ContextJNDISelector) will use the 
  -  specified resource to automatically configure the log4j repository.
  +  specified resource to configure the log4j repository.
   
     <env-entry>
      <description>URL for configuring log4j context</description>
  @@ -78,9 +80,9 @@
      <env-entry-type>java.lang.String</env-entry-type>
     </env-entry>
     
  -  Note that only when "log4j/configuration-resource" environment entry 
  +  Note if the  "log4j/configuration-resource" environment entry 
     is missing, then the logger repository for your application's logging
  -  context will not be configured.
  +  context will NOT be configured.
     
     For more information on the available options see the javadoc for
     org.apache.log4j.selector.ContextJNDISelector.
  @@ -90,9 +92,9 @@
     installing a ServletContextListener which will detach the repository
     from the repository selector and shut it down.
   
  -  The ContextDetachingSCL which ships with log4j does exactly that. To
  -  install it, add the following lines to your web-application's
  -  web.xml file.
  +  The ContextDetachingSCL, where SCL stands ServletContextListener, which 
  +  ships with log4j does exactly that. To install it, add the following 
  +  lines to your web-application's web.xml file.
   
      <listener>
        <listener-class>org.apache.log4j.selector.servlet.ContextDetachingSCL</listener-class>
  @@ -100,31 +102,8 @@
   
     See also the file examples/tiny-webapp/Hello/src/WEB-INF/web.xml
   
  -- You are encouraged to name your web-application in the web
  +- You are also encouraged to name your web-application in the web
     descriptor file. As in
   
     <display-name>Hello sample web-application</display-name>
  -
  -
  -KNOWN PROBLEMS WITH ContextJNDISelector
  -=======================================
  -
  -- In case your J2EE container does not use log4j by default (e.g. T5,
  -  Resin), and you are using ContextJNDISelector to configure multiple
  -  logger repositories, then the default logger repository will be
  -  configured at the same time the logger repository specific for your
  -  first web-application is configured.
  -
  -  For various technical reasons, if that first web-application is
  -  automatically configured using log4j.xml or log4j.properties files
  -  contained in the web-application, then the default logger repository
  -  will be configured using those same configuration files of the
  -  web-application. 
  -
  -  This is usually benign because even if configured with the wrong
  -  file, the default logging respository will probably not be used in
  -  this set up. Nevertheless, you can still correct this error by
  -  forcing log4j to configure the default logging repository with the
  -  configuration file of your choice by setting the
  -  "log4j.configuration" system property.
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message