the "fulldocs" package to get it.
You can also access the javadoc online in the Tomcat
-<a href="http://tomcat.apache.org/tomcat-6.0-doc/">documentation bundle</a>.
+<a href="http://tomcat.apache.org/tomcat-7.0-doc/">documentation bundle</a>.
</body>
</html>
<p>Out of the box, a standard Tomcat 6 installation includes a variety
of pre-installed shared library files, including:</p>
<ul>
-<li>The <em>Servlet 2.5</em> and <em>JSP 2.1</em> APIs that are fundamental
+<li>The <em>Servlet 3.0</em> and <em>JSP 2.1</em> APIs that are fundamental
to writing servlets and JavaServer Pages.<br/><br/></li>
<li>An <em>XML Parser</em> compliant with the JAXP (version 1.2) APIs, so
your application can perform DOM-based or SAX-based processing of
<subsection name="JDK">
-<p>Tomcat 6.0 was designed to run on J2SE 5.0.
+<p>Tomcat 7.0 was designed to run on J2SE 6.0.
</p>
<p>Compatible JDKs for many platforms (or links to where they can be found)
# Context path to install this application on
app.path=/hello
-# Tomcat 6 installation directory
-catalina.home=/usr/local/apache-tomcat-6.0
+# Tomcat 7 installation directory
+catalina.home=/usr/local/apache-tomcat-7.0
# Manager webapp username and password
manager.username=myusername
</section>
-<section name="Checkout or obtain the source code for Tomcat 6.0">
+<section name="Checkout or obtain the source code for Tomcat 7.0">
<p>
Tomcat SVN repository URL:
- <code>http://svn.apache.org/repos/asf/tomcat/tc6.0.x/</code>
+ <code>http://svn.apache.org/repos/asf/tomcat/tc7.0.x/</code>
</p>
<p>
<p>
Checkout the source using SVN, selecting the desired version or
branch (current development source is at
- <code>http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/</code>), or
+ <code>http://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/</code>), or
unpack the source package. The location where the source has been
placed will be referred as ${tomcat.source}.
</p>
Eclipse .project and .classpath files are provided in to root directory of tomcat repository
should allow Eclipse to find all source trees and jars, and
hopefully compile without problems. <b>Note</b> that these
-files assume you are using Eclipse with a 5.0 or later JDK; also, the
-connectors module must be built with a compiler compliance level of 5.0.
+files assume you are using Eclipse with a 6.0 or later JDK.
</p>
<p>
<li><em>jasper-el.jar</em> - Jasper 2 EL implementation.</li>
<li><em>jasper-jdt.jar</em> - Eclipse JDT 3.2 Java compiler.</li>
<li><em>jsp-api.jar</em> - JSP 2.1 API.</li>
- <li><em>servlet-api.jar</em> - Servlet 2.5 API.</li>
+ <li><em>servlet-api.jar</em> - Servlet 3.0 API.</li>
<li><em>tomcat-coyote.jar</em> - Tomcat connectors and utility classes.</li>
<li><em>tomcat-dbcp.jar</em> - package renamed database connection
pool based on Commons DBCP.</li>
<section name="Cluster Basics">
-<p>To run session replication in your Tomcat 6.0 container, the following steps
+<p>To run session replication in your Tomcat 7.0 container, the following steps
should be completed:</p>
<ul>
<li>All your session attributes must implement <code>java.io.Serializable</code></li>
Synchronous vs asynchronous is configured using the <code>channelSendOptions</code>
flag and is an integer value. The default value for the <code>SimpleTcpCluster/DeltaManager</code> combo is
8, which is asynchronous. You can read more on the <a href="tribes/introduction.html">send flag(overview)</a> or the
- <a href="http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/tribes/Channel.html">send flag(javadoc)</a>.
+ <a href="http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/tribes/Channel.html">send flag(javadoc)</a>.
During async replication, the request is returned before the data has been replicated. async replication yields shorter
request times, and synchronous replication guarantees the session to be replicated before the request returns.
</p>
The main element, inside this element all cluster details can be configured.
The <code>channelSendOptions</code> is the flag that is attached to each message sent by the
SimpleTcpCluster class or any objects that are invoking the SimpleTcpCluster.send method.
- The description of the send flags is available at <a href="http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/tribes/Channel.html">
+ The description of the send flags is available at <a href="http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/tribes/Channel.html">
our javadoc site</a>
The <code>DeltaManager</code> sends information using the SimpleTcpCluster.send method, while the backup manager
sends it itself directly through the channel.
</attribute>
<attribute name="soTrafficClass" required="false">
Sets the traffic class level for the socket, the value is between 0 and 255.
- Different values are defined in <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/net/Socket.html#setTrafficClass(int)">
+ Different values are defined in <a href="http://java.sun.com/j2se/1.6.0/docs/api/java/net/Socket.html#setTrafficClass(int)">
java.net.Socket#setTrafficClass(int)</a>.
</attribute>
<attribute name="tcpNoDelay" required="false">
<attribute name="soTrafficClass" required="false">
Sets the traffic class level for the socket, the value is between 0 and 255.
Default value is <code>int soTrafficClass = 0x04 | 0x08 | 0x010;</code>
- Different values are defined in <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/net/Socket.html#setTrafficClass(int)">
+ Different values are defined in <a href="http://java.sun.com/j2se/1.6.0/docs/api/java/net/Socket.html#setTrafficClass(int)">
java.net.Socket#setTrafficClass(int)</a>.
</attribute>
<attribute name="tcpNoDelay" required="false">
</attribute>
<attribute name="socket.performanceConnectionTime" required="false">
<p>(int)The first value for the performance settings. See
- <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/net/Socket.html#setPerformancePreferences(int,%20int,%20int)">Socket Performance Options</a>
+ <a href="http://java.sun.com/j2se/1.6.0/docs/api/java/net/Socket.html#setPerformancePreferences(int,%20int,%20int)">Socket Performance Options</a>
All three performance attributes must be set else the JVM defaults will
be used for all three.</p>
</attribute>
<attribute name="socket.performanceLatency" required="false">
<p>(int)The second value for the performance settings. See
- <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/net/Socket.html#setPerformancePreferences(int,%20int,%20int)">Socket Performance Options</a>
+ <a href="http://java.sun.com/j2se/1.6.0/docs/api/java/net/Socket.html#setPerformancePreferences(int,%20int,%20int)">Socket Performance Options</a>
All three performance attributes must be set else the JVM defaults will
be used for all three.</p>
</attribute>
<attribute name="socket.performanceBandwidth" required="false">
<p>(int)The third value for the performance settings. See
- <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/net/Socket.html#setPerformancePreferences(int,%20int,%20int)">Socket Performance Options</a>
+ <a href="http://java.sun.com/j2se/1.6.0/docs/api/java/net/Socket.html#setPerformancePreferences(int,%20int,%20int)">Socket Performance Options</a>
All three performance attributes must be set else the JVM defaults will
be used for all three.</p>
</attribute>
behind a firewall. Only this port is configured via the listener. The
remainder of the configuration is via the standard system properties for
configuring JMX. For further information on configuring JMX see
- <a href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html">
+ <a href="http://java.sun.com/j2se/1.6.0/docs/guide/management/agent.html">
Monitoring and Management Using JMX</a> included with the Java SDK
documentation.</p>
</table>
<xsl:apply-templates select="readme"/>
<hr size="1" />
- <h3>Apache Tomcat/6.0</h3>
+ <h3>Apache Tomcat/7.0</h3>
</body>
</html>
</xsl:template>
The TCD is not packaged with the Tomcat core
distribution, and must therefore be downloaded separately from
the Downloads area. The download is usually labelled
- <i>apache-tomcat-6.0.x-deployer</i>.
+ <i>apache-tomcat-7.0.x-deployer</i>.
</p>
<p>
TCD has prerequisites of Apache Ant 1.6.2+ and a Java installation.
<code>compile</code> (default): Compile and validate the web
application. This can be used standalone, and does not need a running
Tomcat server. The compiled application will only run on the associated
- Tomcat 6.0.x server release, and is not guaranteed to work on another
+ Tomcat 7.0.x server release, and is not guaranteed to work on another
Tomcat release, as the code generated by Jasper depends on its runtime
component. It should also be noted that this target will also compile
automatically any Java source file located in the
<section name="Introduction">
<p>This is the top-level entry point of the documentation bundle for the
-<strong>Apache Tomcat</strong> Servlet/JSP container. Apache Tomcat version 6.0
+<strong>Apache Tomcat</strong> Servlet/JSP container. Apache Tomcat version 7.0
implements the
-Servlet 2.5 and JavaServer Pages 2.1 specifications from the
+Servlet 3.0 and JavaServer Pages 2.1 specifications from the
<a href="http://www.jcp.org">Java Community Process</a>, and includes many
additional features that make it a useful platform for developing and deploying
web applications and web services.</p>
- Complete documentation and HOWTOs on the JK native webserver connector,
used to interface Apache Tomcat with servers like Apache HTTPd, IIS
and others.</li>
+<!-- TODO SERVLET3 Update when URL is available -->
<li><a href="http://java.sun.com/products/servlet/2.5/docs/servlet-2_5-mr2/index.html">
<strong>Servlet API Javadocs</strong></a> - The Servlet 2.5 API Javadocs.</li>
<li><a href="http://java.sun.com/products/jsp/2.1/docs/jsp-2_1-pfd2/index.html">
<section name="Introduction">
-<p>Tomcat 6.0 uses the Jasper 2 JSP Engine to implement
-the <a href="http://java.sun.com/products/jsp/">JavaServer Pages 2.0</a>
+<p>Tomcat 7.0 uses the Jasper 2 JSP Engine to implement
+the <a href="http://java.sun.com/products/jsp/">JavaServer Pages 2.1</a>
specification.</p>
<p>Jasper 2 has been redesigned to significantly improve performance over
<b>Please note that JNDI resource configuration changed somewhat between
Tomcat 5.0.x and Tomcat 5.5.x.</b> You will most likely need to modify older
JNDI resource configurations to match the syntax in the example below in order
-to make them work in Tomcat 6.x.x.
+to make them work in Tomcat 7.x.x.
</p>
<p>
<section name="Introduction">
<p>
- Tomcat 6.0 uses
+ Tomcat 7.0 uses
<a href="http://commons.apache.org/logging">Commons Logging</a>
throughout its internal code allowing the
developer to choose a logging configuration that suits their needs, e.g
logging implementation.
</p>
<p>
- An important consequence for Tomcat 6.0 is that the <Logger> element found in
+ An important consequence for Tomcat 7.0 is that the <Logger> element found in
previous versions to create a <code>localhost_log</code> is no longer a valid nested element
of <Context>. 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
<section name="log4j">
<p>
- Tomcat 6.0 has done away with <code>localhost_log</code> which you may be familiar with
+ Tomcat 7.0 has done away with <code>localhost_log</code> which you may be familiar with
as the runtime exception/stack trace log. These types of error are usually thrown
by uncaught exceptions, but are still valuable to the developer. They can now be
found in the <code>stdout</code> log.
constructs which allows more freedom for defining handlers and assigning them to loggers.
</p>
<p>
- JULI is enabled by default in Tomcat 6.0, and supports per classloader configuration, in addition to
+ JULI is enabled by default in Tomcat 7.0, and supports per classloader configuration, in addition to
the regular global java.util.logging configuration. This means that logging can be configured at
the following layers:
<ul>
<li>A prefix may be added to handler names, so that multiple handlers of a single class may be
instantiated. A prefix is a String which starts with a digit, and ends with '.'. For example,
<code>22foobar.</code> is a valid prefix.</li>
- <li>As in Java 5.0, loggers can define a list of handlers using the <code>loggerName.handlers</code>
+ <li>As in Java 6.0, loggers can define a list of handlers using the <code>loggerName.handlers</code>
property.</li>
<li>By default, loggers will not delegate to their parent if they have associated handlers. This
may be changed per logger using the <code>loggerName.useParentHandlers</code> property, which accepts
<section name="Enabling JMX Remote">
<p>The Sun website includes the list of options and how to configure JMX Remote on Java 5:
- <a href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html">
- http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html</a>.
+ <a href="http://java.sun.com/j2se/1.6.0/docs/guide/management/agent.html">
+ http://java.sun.com/j2se/1.6.0/docs/guide/management/agent.html</a>.
</p>
- <p>The following is a quick configuration guide for Java 5:</p>
+ <p>The following is a quick configuration guide for Java 6:</p>
<p>Add the following parameters to your Tomcat startup script:
<source>
set CATALINA_OPTS="-Dcom.sun.management.jmxremote \
<project name="Apache Tomcat Documentation"
href="http://tomcat.apache.org/">
- <title>Apache Tomcat 6.0</title>
+ <title>Apache Tomcat 7.0</title>
<logo href="/images/tomcat.gif">
The Apache Tomcat Servlet/JSP Container
projects / tomcat7.0 / commitdiff