tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r...@apache.org
Subject cvs commit: jakarta-tomcat-catalina/catalina/src/conf catalina.policy
Date Thu, 03 Mar 2005 23:41:15 GMT
remm        2005/03/03 15:41:14

  Modified:    webapps/docs logging.xml
               catalina/src/conf catalina.policy
  Log:
  - Add JULI in the policy file.
  - Modify the header of the logging page in the docs.
  
  Revision  Changes    Path
  1.7       +5 -5      jakarta-tomcat-catalina/webapps/docs/logging.xml
  
  Index: logging.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/logging.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- logging.xml	3 Mar 2005 18:26:40 -0000	1.6
  +++ logging.xml	3 Mar 2005 23:41:14 -0000	1.7
  @@ -20,7 +20,7 @@
       <a href="http://jakarta.apache.org/commons/logging">Commons Logging</a>
       throughout its internal code allowing the 
       developer to choose a logging configuration that suits their needs, e.g
  -    JDK Logging or 
  +    java.util.logging or 
       <a href="http://logging.apache.org/log4j">Log4J</a>. 
       Commons Logging provides Tomcat the ability to log
       hierarchially across various log levels without needing to rely on a particular
  @@ -29,10 +29,10 @@
     <p>
       An important consequence for Tomcat 5.5 is that the &lt;Logger&gt; element
found in 
       previous versions to create a <code>localhost_log</code> is no longer a
valid nested element 
  -    of &lt;Context&gt;. Instead, <code>stdout</code> will collect runtime
exceptions and other uncaught
  -    exception generated by web applications. If the developer wishes to collect detailed
internal 
  -    Tomcat logging (i.e what is happening within the Tomcat engine), then they should configure

  -    a logging system such as JDK Logging or log4j as detailed next.
  +    of &lt;Context&gt;. Instead, the default Tomcat configuration will use java.util.logging.

  +    If the developer wishes to collect detailed internal Tomcat logging (i.e what is happening

  +    within the Tomcat engine), then they should configure a logging system such as java.util.logging

  +    or log4j as detailed next.
     </p>
   
     </section>
  
  
  
  1.13      +6 -1      jakarta-tomcat-catalina/catalina/src/conf/catalina.policy
  
  Index: catalina.policy
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/catalina.policy,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- catalina.policy	15 Sep 2004 18:57:41 -0000	1.12
  +++ catalina.policy	3 Mar 2005 23:41:14 -0000	1.13
  @@ -65,6 +65,11 @@
           permission java.security.AllPermission;
   };
   
  +// These permissions apply to JULI
  +grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
  +        permission java.security.AllPermission;
  +};
  +
   // These permissions apply to the servlet API classes
   // and those that are shared across all class loaders
   // located in the "common" directory
  
  
  

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


Mime
View raw message