tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yo...@apache.org
Subject cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configwebcom.xml installhowto.xml
Date Wed, 11 Aug 2004 18:06:28 GMT
yoavs       2004/08/11 11:06:27

  Modified:    jk/xdocs/jk2 configwebcom.xml installhowto.xml
  Log:
  Corrected docs per email comments to tomcat-dev in thread titled
  Request: Webpage update "jakarta.apache.org/tomcat/connectors-doc/jk2/jk2/" for IIS-Setup
  
  Revision  Changes    Path
  1.19      +62 -42    jakarta-tomcat-connectors/jk/xdocs/jk2/configwebcom.xml
  
  Index: configwebcom.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configwebcom.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- configwebcom.xml	26 May 2004 07:06:00 -0000	1.18
  +++ configwebcom.xml	11 Aug 2004 18:06:27 -0000	1.19
  @@ -15,51 +15,71 @@
      See the License for the specific language governing permissions and
      limitations under the License.
   </copyright>
  +
   <properties>
  -<title>Components</title>
  -<author email="cmanolache@yahoo.com">Costin Manolache</author>
  -<author email="jfrederic.clere@fujitsu-siemens.com">Jean-Frederic Clere</author>
  -<date>$Date$</date>
  +  <title>Components</title>
  +
  +  <author email="cmanolache@yahoo.com">Costin Manolache</author>
  +  <author email="jfrederic.clere@fujitsu-siemens.com">Jean-Frederic Clere</author>
  +  <author email="yoavs@apache.org">Yoav Shapira</author>
  +
  +  <date>$Date$</date>
   </properties>
  -    <section name="Intro"><p>Each component instance has a name, that is used
for configuration and at runtime. Each component has a number of configurable properties.
The following rules are used:
  -<ul><li>The name is composed from the type and a local part, separated with
a ':' ( example: channel.unixsocket:/tmp/jk.socket ) </li>
  -<li>The 'type' consist of '.' and ascii characters.  It is mapped to a JMX 'domain'.
 </li>
  -<li>The local part consists of ascii characters and .:/; 
  -<p>Note that '=,' are not currently allowed - a future version may support the jmx
syntax by using quotes to separate the local part from the property and value ( in .properties
mode we must use '=' to separate the value from type, local name and property name ). </p></li>
  -<li>The property is a simple name, with no dots. </li>
  -<li>A simple form of substitution is used in values, where $(property) will be replaced
with a previously defined setting. If the property has ':' in it, it'll take the value from
the object, if not it'll take the value from a global map.</li></ul></p>
  +
  +<section name="Intro">
  +  <p>
  +    Each component instance has a name, that is used for configuration and at runtime.
  +    Each component has a number of configurable properties. The following rules are used:
  +    <ul>
  +      <li>The name is composed from the type and a local part, separated with a ':'
( example: channel.unixsocket:/tmp/jk.socket ) </li>
  +      <li>The 'type' consist of '.' and ascii characters.  It is mapped to a JMX
'domain'.  </li>
  +      <li>The local part consists of ascii characters and .:/; 
  +
  +        <p>
  +          Note that '=,' are not currently allowed - a future version may support the jmx
syntax by using quotes to separate the local part from the property and value ( in .properties
mode we must use '=' to separate the value from type, local name and property name ).
  +        </p>
  +      </li>
  +      <li>The property is a simple name, with no dots. </li>
  +      <li>A simple form of substitution is used in values, where $(property) will
be replaced with a previously defined setting. If the property has ':' in it, it'll take the
value from the object, if not it'll take the value from a global map.
  +      </li>
  +    </ul>
  +  </p>
   </section>
  -        <section name="Common properties">
  -            <p>Common properties for all components</p>
  -            <p>
  -                <table>
  -                    <tr>
  -                        <th>Property name</th>
  -                        <th>Default</th>
  -                        <th>Description</th>
  -                    </tr>
  -                    <tr>
  -                        <td>disabled</td>
  -                        <td>0 (false)</td>
  -                        <td>"disabled" state for the component, 1=true 0=false</td>
  -                    </tr>
  -                    <tr>
  -                        <td>debug</td>
  -                        <td>0 (false)</td>
  -                        <td>Debug level for the component, 0=disabled, 1..10 enabled.
Higher levels
  -                            generate more debug.</td>
  -                    </tr>
  -                    <tr>
  -                        <td>version</td>
  -                        <td>0</td>
  -                        <td>'Generation' of the component config. Important for runtime
reconfiguration.
  -                            If you edit the config file or set the shmem properties, you
need to also
  -                            upgrade the version of the modified component. The config layer
will detect
  -                            the change and call the setter method.</td>
  -                     </tr>
  -                </table>
  -            </p>
  -        </section>
  +
  +<section name="Common properties">
  +  <p>
  +    Common properties for all components
  +  </p>
  +  <p>
  +    <table>
  +      <tr>
  +        <th>Property name</th>
  +        <th>Default</th>
  +        <th>Description</th>
  +      </tr>
  +      <tr>
  +        <td>disabled</td>
  +        <td>0 (false)</td>
  +        <td>"disabled" state for the component, 1=true 0=false</td>
  +      </tr>
  +      <tr>
  +        <td>debug</td>
  +        <td>0 (false)</td>
  +        <td>Debug level for the component, 0=disabled, 1..10 enabled. Higher levels
  +            generate more debug information.</td>
  +      </tr>
  +      <tr>
  +        <td>ver (short for, and formerly known as, version)</td>
  +        <td>0</td>
  +        <td>'Generation' of the component config. Important for runtime reconfiguration.
  +            If you edit the config file or set the shmem properties, you need to also
  +            upgrade the version of the modified component. The config layer will detect
  +            the change and call the setter method.</td>
  +      </tr>
  +    </table>
  +  </p>
  +</section>
  +
           <section name="workerEnv">
               <p>This component represent the core jk2, it has the default logger for
all other components. Is the central controller, it controls global properties
   and  provides access to all other objects</p>
  
  
  
  1.8       +12 -5     jakarta-tomcat-connectors/jk/xdocs/jk2/installhowto.xml
  
  Index: installhowto.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/installhowto.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- installhowto.xml	4 Mar 2004 04:46:34 -0000	1.7
  +++ installhowto.xml	11 Aug 2004 18:06:27 -0000	1.8
  @@ -15,12 +15,17 @@
      See the License for the specific language governing permissions and
      limitations under the License.
   </copyright>
  +
   <properties>
  -<title>Installation of jk2 in the Web Server</title>
  -<author email="jfrederic.clere@fujitsu-siemens.com">Jean-Frederic Clere</author>
  -<author email="andy@tagish.com">Andy Armstrng</author>
  -<date>$Date$</date>
  +  <title>Installation of jk2 in the Web Server</title>
  +
  +  <author email="jfrederic.clere@fujitsu-siemens.com">Jean-Frederic Clere</author>
  +  <author email="andy@tagish.com">Andy Armstrng</author>
  +  <author email="yoavs@apache.org">Yoav Shapira</author>
  +
  +  <date>$Date$</date>
   </properties>
  +
     <section name="Installation">
       <p>
         The actual build mechanism creates the dso files in the
  @@ -104,7 +109,9 @@
               <b>"HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi
Redirector\2.0"</b>
               </li><li>
               Add a string value with the name <b>serverRoot</b> and a value
which is a full path
  -            to your Tomcat installation (for example <b>c:\jakarta-tomcat</b>)
  +            to your Tomcat installation (for example <b>c:\jakarta-tomcat</b>).
 If Tomcat is installed
  +            on a different server, this entry must point to the location (directory) where
the
  +            workers2.properties file resides.
               </li><li>
               Add a string value with the name <b>extensionUri</b> and a value
of <b>/jakarta/isapi_redirector2.dll</b>
               </li><li>
  
  
  

---------------------------------------------------------------------
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