You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ma...@apache.org on 2017/05/11 07:16:17 UTC

svn commit: r1794790 - in /tomcat/site/trunk: docs/migration-8.html xdocs/migration-8.xml

Author: markt
Date: Thu May 11 07:16:17 2017
New Revision: 1794790

URL: http://svn.apache.org/viewvc?rev=1794790&view=rev
Log:
Add section on Jar scanning

Modified:
    tomcat/site/trunk/docs/migration-8.html
    tomcat/site/trunk/xdocs/migration-8.xml

Modified: tomcat/site/trunk/docs/migration-8.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-8.html?rev=1794790&r1=1794789&r2=1794790&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-8.html (original)
+++ tomcat/site/trunk/docs/migration-8.html Thu May 11 07:16:17 2017
@@ -242,6 +242,9 @@
 <a href="#JavaServer_Pages_2.3">JavaServer Pages 2.3</a>
 </li>
 <li>
+<a href="#Jar_Scanning">Jar Scanning</a>
+</li>
+<li>
 <a href="#Default_connector_implementation">Default connector implementation</a>
 </li>
 <li>
@@ -403,6 +406,42 @@ of Apache Tomcat.</p>
   
 </div>
 </div>
+
+  
+<div class="subsection">
+<h4 id="Jar_Scanning">Jar Scanning</h4>
+<div class="text">
+
+    
+<p>During the implementation of Servlet 3.1 a number of errors were
+    identified in Tomcat 7's Servlet 3.0 pluggability implementation.
+    Specifically:</p>
+
+    
+<ul>
+    
+<li>the SCI scan did not obey class loader ordering;</li>
+    
+<li>fragments in container JARs were processed rather than ignored;</li>
+    
+<li>container provided SCIs were sometimes ignored.</li>
+    
+</ul>
+
+    
+<p>These issues were corrected for Tomcat 8 but not back-ported to Tomcat 7
+    because the fixed required significant API changes to the
+    <code>JarScanner</code> component as well as changes to the configuration
+    options.</p>
+
+    
+<p>When migrating to Tomcat 8, Jar scanning configurations will need to be
+    reviewed and adjusted for the new configuration options and custom
+    <code>JarScanner</code> implementations will need to be updated to implement
+    the new API.</p>    
+  
+</div>
+</div>
 
   
 <div class="subsection">

Modified: tomcat/site/trunk/xdocs/migration-8.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-8.xml?rev=1794790&r1=1794789&r2=1794790&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-8.xml (original)
+++ tomcat/site/trunk/xdocs/migration-8.xml Thu May 11 07:16:17 2017
@@ -86,6 +86,29 @@ of Apache Tomcat.</p>
 
   </subsection>
 
+  <subsection name="Jar Scanning">
+
+    <p>During the implementation of Servlet 3.1 a number of errors were
+    identified in Tomcat 7's Servlet 3.0 pluggability implementation.
+    Specifically:</p>
+
+    <ul>
+    <li>the SCI scan did not obey class loader ordering;</li>
+    <li>fragments in container JARs were processed rather than ignored;</li>
+    <li>container provided SCIs were sometimes ignored.</li>
+    </ul>
+
+    <p>These issues were corrected for Tomcat 8 but not back-ported to Tomcat 7
+    because the fixed required significant API changes to the
+    <code>JarScanner</code> component as well as changes to the configuration
+    options.</p>
+
+    <p>When migrating to Tomcat 8, Jar scanning configurations will need to be
+    reviewed and adjusted for the new configuration options and custom
+    <code>JarScanner</code> implementations will need to be updated to implement
+    the new API.</p>    
+  </subsection>
+
   <subsection name="Default connector implementation">
 
     <p>The default HTTP and AJP connector implementation has switched from the



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org