remm        2003/07/30 11:37:51

  Modified:    webapps/docs/config context.xml engine.xml host.xml
                        resources.xml
  Log:
  - Document the background processing feature.
  - Document configuration of the resource cache.
  
  Revision  Changes    Path
  1.5       +22 -3     jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- context.xml       15 Jan 2003 03:40:44 -0000      1.4
  +++ context.xml       30 Jul 2003 18:37:51 -0000      1.5
  @@ -47,10 +47,13 @@
   
     <p>In addition to nesting <strong>Context</strong> elements inside a
     <a href="host.html">Host</a> element, you can also store them in
  -  individual files (with a ".xml" extension) in the <code>appBase</code>
  -  directory for a Host.  See
  +  individual files (with a ".xml" extension) in the 
  +  <code>$CATALINA_HOME/conf/[enginename]/[hostname]/</code> directory.  See
     <a href="host.html#Automatic Application Deployment">Automatic
  -  Application Deployment</a> for more information.</p>
  +  Application Deployment</a> for more information. This method allows dynamic
  +  reconfiguration of the web application, since the main 
  +  <code>conf/server.xml</code> file cannot be reloaded without restarting
  +  Tomcat.</p>
   
     <p>In addition to explicitly specified Context elements, there are
     several techniques by which Context elements can be created automatically
  @@ -80,6 +83,22 @@
       support the following attributes:</p>
   
       <attributes>
  +
  +      <attribute name="backgroundProcessorDelay" required="false">
  +        <p>This value represents the delay in seconds between the 
  +        invocation of the backgroundProcess method on this context and 
  +        its child containers, including all wrappers. 
  +        Child containers will not be invoked if their delay value is not 
  +        negative (which would mean they are using their own processing 
  +        thread). Setting this to a positive value will cause 
  +        a thread to be spawn. After waiting the specified amount of time, 
  +        the thread will invoke the backgroundProcess method on this host 
  +        and all its child containers. A context will use background 
  +        processing to perform session expiration and class monitoring for
  +        reloading. If not specified, the default value for this attribute is 
  +        -1, which means the context will rely on the background processing 
  +        thread of its parent host.</p>
  +      </attribute>
   
         <attribute name="className" required="false">
           <p>Java class name of the implementation to use.  This class must
  
  
  
  1.4       +13 -0     jakarta-tomcat-catalina/webapps/docs/config/engine.xml
  
  Index: engine.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/engine.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- engine.xml        15 Jan 2003 03:40:44 -0000      1.3
  +++ engine.xml        30 Jul 2003 18:37:51 -0000      1.4
  @@ -39,6 +39,19 @@
   
       <attributes>
   
  +      <attribute name="backgroundProcessorDelay" required="false">
  +        <p>This value represents the delay in seconds between the 
  +        invocation of the backgroundProcess method on this engine and 
  +        its child containers, including all hosts and contexts. 
  +        Child containers will not be invoked if their delay value is not 
  +        negative (which would mean they are using their own processing 
  +        thread). Setting this to a positive value will cause 
  +        a thread to be spawn. After waiting the specified amount of time, 
  +        the thread will invoke the backgroundProcess method on this engine 
  +        and all its child containers. If not specified, the default value for
  +        this attribute is 10, which represent a 10 seconds delay.</p>
  +      </attribute>
  +
         <attribute name="className" required="false">
           <p>Java class name of the implementation to use.  This class must
           implement the <code>org.apache.catalina.Engine</code> interface.
  
  
  
  1.5       +17 -1     jakarta-tomcat-catalina/webapps/docs/config/host.xml
  
  Index: host.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/host.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- host.xml  28 Jun 2003 18:48:59 -0000      1.4
  +++ host.xml  30 Jul 2003 18:37:51 -0000      1.5
  @@ -78,6 +78,22 @@
           Deployment</a> for more information.</p>
         </attribute>
   
  +      <attribute name="backgroundProcessorDelay" required="false">
  +        <p>This value represents the delay in seconds between the 
  +        invocation of the backgroundProcess method on this host and 
  +        its child containers, including all contexts. 
  +        Child containers will not be invoked if their delay value is not 
  +        negative (which would mean they are using their own processing 
  +        thread). Setting this to a positive value will cause 
  +        a thread to be spawn. After waiting the specified amount of time, 
  +        the thread will invoke the backgroundProcess method on this host 
  +        and all its child containers. A host will use background processing to
  +        perform live web application deployment related tasks. If not 
  +        specified, the default value for this attribute is -1, which means 
  +        the host will rely on the background processing thread of its parent 
  +        engine.</p>
  +      </attribute>
  +
         <attribute name="className" required="false">
           <p>Java class name of the implementation to use.  This class must
           implement the <code>org.apache.catalina.Host</code> interface.
  @@ -288,7 +304,7 @@
       automatically deployed, according to the rules described above. The 
       auto deployer will also track web applications for the following changes:
       <ul>
  -        <li>An update to the conf/web.xml file will trigger a reload of the
  +        <li>An update to the WEB-INF/web.xml file will trigger a reload of the
           web application</li>
           <li>An update to a WAR which has been expanded will trigger 
           an undeploy (<strong>with a removal of the expanded webapp</strong>), 
  
  
  
  1.3       +6 -0      jakarta-tomcat-catalina/webapps/docs/config/resources.xml
  
  Index: resources.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/resources.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- resources.xml     15 Jan 2003 03:40:44 -0000      1.2
  +++ resources.xml     30 Jul 2003 18:37:51 -0000      1.3
  @@ -81,6 +81,12 @@
           defaults to <code>true</code>.</p>
         </attribute>
   
  +      <attribute name="cacheMaxSize" required="false">
  +        <p>Maximum size in kilobytes (KB) of the cache associated with 
  +        the resources, if cached is set to true. It defaults 
  +        to <code>10240</code> (10 megabytes).</p>
  +      </attribute>
  +
         <attribute name="caseSensitive" required="false">
           <p>This boolean flag toggles case sensitivity for resourceson 
           the Windows platform. Defaults to <code>true</code>.</p>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to