Author: markt
Date: Mon Sep 8 13:22:45 2014
New Revision: 1623387
URL: http://svn.apache.org/r1623387
Log:
Add a not about the changes introduced to fix bug 55943.
Modified:
tomcat/site/trunk/docs/migration-7.html
tomcat/site/trunk/xdocs/migration-7.xml
Modified: tomcat/site/trunk/docs/migration-7.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-7.html?rev=1623387&r1=1623386&r2=1623387&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-7.html (original)
+++ tomcat/site/trunk/docs/migration-7.html Mon Sep 8 13:22:45 2014
@@ -265,6 +265,9 @@
<a href="#Upgrading_7.0.x">Upgrading 7.0.x</a>
<ol>
<li>
+<a href="#Tomcat_7.0.x_noteable_changes">Tomcat 7.0.x noteable changes</a>
+</li>
+<li>
<a href="#Tomcat_7.0.x_configuration_file_differences">Tomcat 7.0.x
configuration file differences</a>
</li>
</ol>
@@ -953,13 +956,25 @@ of Apache Tomcat.</p>
<h3 id="Upgrading_7.0.x">Upgrading 7.0.x</h3>
<div class="text">
-<p>When upgrading instances of Apache Tomcat from one version of Tomcat 7 to
- another, particularly when using separate locations for $CATALINA_HOME and
- $CATALINA_BASE, it is necessary to ensure that any changes in the
- configuration files such as new attributes and changes to defaults are
applied
- as part of the upgrade. To assist with the identification of these changes,
- the form below may be used to view the differences between the configuration
- files in different versions of Tomcat 7.</p>
+<div class="subsection">
+<h4 id="Tomcat_7.0.x_noteable_changes">Tomcat 7.0.x noteable changes</h4>
+<div class="text">
+
+<p>The Tomcat developers aim for each patch release to be fully backwards
+ compatible with the previous release. Occassionally, it is necessary to
+ break backwards compatibility in order to fix a bug. In most cases,
these
+ changes will go unnoticed. This section lists changes that are not fully
+ backwards compatible and might cause breakage when upgrading.</p>
+
+<ul>
+
+<li>In 7.0.51 onwards, the web application class loader is now a higher
+ priority for loading classes than the system class loader.</li>
+
+</ul>
+
+</div>
+</div>
<div class="subsection">
@@ -967,6 +982,15 @@ of Apache Tomcat.</p>
<div class="text">
+<p>When upgrading instances of Apache Tomcat from one version of Tomcat 7 to
+ another, particularly when using separate locations for $CATALINA_HOME and
+ $CATALINA_BASE, it is necessary to ensure that any changes in the
+ configuration files such as new attributes and changes to defaults are
+ applied as part of the upgrade. To assist with the identification of these
+ changes, the form below may be used to view the differences between the
+ configuration files in different versions of Tomcat 7.</p>
+
+
<p>Select a configuration file, old version and new version from the boxes
below and then click "View differences" to see the differences.
The differences will be shown in a new tab/window.</p>
Modified: tomcat/site/trunk/xdocs/migration-7.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-7.xml?rev=1623387&r1=1623386&r2=1623387&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-7.xml (original)
+++ tomcat/site/trunk/xdocs/migration-7.xml Mon Sep 8 13:22:45 2014
@@ -463,16 +463,28 @@ of Apache Tomcat.</p>
</section>
<section name="Upgrading 7.0.x">
- <p>When upgrading instances of Apache Tomcat from one version of Tomcat 7 to
- another, particularly when using separate locations for $CATALINA_HOME and
- $CATALINA_BASE, it is necessary to ensure that any changes in the
- configuration files such as new attributes and changes to defaults are
applied
- as part of the upgrade. To assist with the identification of these changes,
- the form below may be used to view the differences between the configuration
- files in different versions of Tomcat 7.</p>
+ <subsection name="Tomcat 7.0.x noteable changes">
+ <p>The Tomcat developers aim for each patch release to be fully backwards
+ compatible with the previous release. Occassionally, it is necessary to
+ break backwards compatibility in order to fix a bug. In most cases,
these
+ changes will go unnoticed. This section lists changes that are not fully
+ backwards compatible and might cause breakage when upgrading.</p>
+ <ul>
+ <li>In 7.0.51 onwards, the web application class loader is now a higher
+ priority for loading classes than the system class loader.</li>
+ </ul>
+ </subsection>
<subsection name="Tomcat 7.0.x configuration file differences">
+ <p>When upgrading instances of Apache Tomcat from one version of Tomcat 7
to
+ another, particularly when using separate locations for $CATALINA_HOME and
+ $CATALINA_BASE, it is necessary to ensure that any changes in the
+ configuration files such as new attributes and changes to defaults are
+ applied as part of the upgrade. To assist with the identification of these
+ changes, the form below may be used to view the differences between the
+ configuration files in different versions of Tomcat 7.</p>
+
<p>Select a configuration file, old version and new version from the boxes
below and then click "View differences" to see the differences.
The differences will be shown in a new tab/window.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
