craigmcc 02/02/13 23:06:36
Modified: webapps/tomcat-docs class-loader-howto.xml manager-howto.xml
webapps/tomcat-docs/appdev build.xml.txt
Log:
Miscellaneous typo corrections to the documentation and sample build.xml file.
Revision Changes Path
1.6 +35 -2 jakarta-tomcat-4.0/webapps/tomcat-docs/class-loader-howto.xml
Index: class-loader-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/class-loader-howto.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- class-loader-howto.xml 29 Jan 2002 15:23:50 -0000 1.5
+++ class-loader-howto.xml 14 Feb 2002 07:06:35 -0000 1.6
@@ -105,8 +105,10 @@
applications. Normally, application classes should <strong>NOT</strong>
be placed here. All unpacked classes and resources in
<code>$CATALINA_HOME/common/classes</code>, as well as classes and
- resources in JAR files under
- <code>$CATALINA_HOME/common/lib</code>, are made visible through this
+ resources in JAR files under the
+ <code>$CATALINA_HOME/commons/endorsed</code> and
+ <code>$CATALINA_HOME/common/lib</code> directories,
+ are made visible through this
class loader. By default, that includes the following:
<ul>
<li><em>jndi.jar</em> - The Java Naming and Directory Interface API
@@ -203,12 +205,43 @@
<li>Bootstrap classes of your JVM</li>
<li>System class loader classses (described above)</li>
<li><em>$CATALINA_HOME/common/classes</em></li>
+<li><em>$CATALINA_HOME/common/endorsed/*.jar</em></li>
<li><em>$CATALINA_HOME/common/lib/*.jar</em></li>
<li><em>$CATALINA_HOME/shared/classes</em></li>
<li><em>$CATALINA_HOME/shared/lib/*.jar</em></li>
</ul>
</section>
+
+
+<section name="XML Parsers and JDK 1.4">
+
+<p>Among many other changes, the JDK 1.4 release packages the JAXP APIs, and
+a version of Xerces, inside the JDK. This has impacts on applications that
+wish to use their own XML parser.</p>
+
+<p>In previous versions of Tomcat 4, you could simply replace the XML parser
+in the <code>$CATALINA_HOME/common/lib</code> directory to change the parser
+used by all web applications. However, this technique will not be effective
+when you are running on JDK 1.4, because the usual class loader delegation
+process will always choose the implementation inside the JDK in preference
+to this one.</p>
+
+<p>JDK 1.4 supports a mechanism called the "Endorsed Standards Override
+Mechanism" to allow replacement of APIs created outside of the JCP (i.e.
+DOM and SAX from W3C). It can also be used to update the XML parser
+implementation. For more information, see:
+<a href="http://java.sun.com/j2se/1.4/docs/guide/standards/index.html";>
+http://java.sun.com/j2se/1.4/docs/guide/standards/index.html</a>.</p>
+
+<p>Tomcat utilizes this mechanism by including the system property setting
+<code>-Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed</code> in the
+command line that starts the container. Therefore, you can replace the
+parser that is installed in this directory, and it will get used even on a
+JDK 1.4 system.</p>
+
+</section>
+
</body>
1.9 +6 -6 jakarta-tomcat-4.0/webapps/tomcat-docs/manager-howto.xml
Index: manager-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/manager-howto.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- manager-howto.xml 12 Feb 2002 22:14:02 -0000 1.8
+++ manager-howto.xml 14 Feb 2002 07:06:35 -0000 1.9
@@ -642,20 +642,20 @@
... construct web application in ${build} subdirectory ...
</target>
- <target name="deploy" description="Deploy web application"
+ <target name="install" description="Install web application"
depends="compile">
- <deploy url="${url}" username="${username}" password="${password}"
+ <install url="${url}" username="${username}" password="${password}"
path="${path}" war="file://${build}"/>
</target>
<target name="reload" description="Reload web application"
depends="compile">
<reload url="${url}" username="${username}" password="${password}"
- path="${path}" war="file://${build}"/>
+ path="${path}"/>
</target>
- <target name="undeploy" description="Undeploy and delete web application">
- <deploy url="${url}" username="${username}" password="${password}"
+ <target name="remove" description="Remove web application">
+ <remove url="${url}" username="${username}" password="${password}"
path="${path}"/>
</target>
@@ -663,7 +663,7 @@
</pre></td></tr>
</table>
-<p>Now, you can execute commands like <code>ant deploy</code> to deploy the
+<p>Now, you can execute commands like <code>ant install</code> to install th
applcation to a running instance of Tomcat, or <code>ant reload</code> to
tell Tomcat to reload it. Note also that most of the interesting values in
this <code>build.xml</code> file are defined as replaceable properties, so
1.5 +7 -2 jakarta-tomcat-4.0/webapps/tomcat-docs/appdev/build.xml.txt
Index: build.xml.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/appdev/build.xml.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- build.xml.txt 29 Jan 2002 19:32:11 -0000 1.4
+++ build.xml.txt 14 Feb 2002 07:06:36 -0000 1.5
@@ -18,7 +18,7 @@
image files), including the WEB-INF subdirectory
and its configuration file contents.
- $Id: build.xml.txt,v 1.4 2002/01/29 19:32:11 craigmcc Exp $
+ $Id: build.xml.txt,v 1.5 2002/02/14 07:06:36 craigmcc Exp $
-->
@@ -218,6 +218,9 @@
<!-- Include all elements that Tomcat exposes to applications -->
<pathelement location="${catalina.home}/common/classes"/>
+ <fileset dir="${catalina.home}/common/endorsed">
+ <include name="*.jar"/>
+ </fileset>
<fileset dir="${catalina.home}/common/lib">
<include name="*.jar"/>
</fileset>
@@ -320,7 +323,7 @@
</copy>
<!-- Create application JAR file -->
- <jar jarfile="${dist.home}/${app.name}=${app.version}.war"
+ <jar jarfile="${dist.home}/${app.name}-${app.version}.war"
basedir="${build.home}"/>
<!-- Copy additional files to ${dist.home} as necessary -->
@@ -345,6 +348,8 @@
NOTE: This target will only succeed if it is run from the same server that
Tomcat is running on.
+
+ NOTE: This is the logical opposite of the "remove" target.
-->
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
