Author: markt
Date: Tue Mar  3 20:48:02 2015
New Revision: 1663787

URL: http://svn.apache.org/r1663787
Log:
Add a deployment section to the Tomcat 8 migration guide
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=1663787&r1=1663786&r2=1663787&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-8.html (original)
+++ tomcat/site/trunk/docs/migration-8.html Tue Mar  3 20:48:02 2015
@@ -232,6 +232,9 @@
 <li>
 <a href="#Internal_APIs">Internal APIs</a>
 </li>
+<li>
+<a href="#Deployment">Deployment</a>
+</li>
 </ol>
 </li>
 <li>
@@ -536,6 +539,51 @@ of Apache Tomcat.</p>
     
 </ul>
 
+  
+</div>
+</div>
+
+  
+<div class="subsection">
+<h4 id="Deployment">Deployment</h4>
+<div class="text">
+
+    
+<p>Deployment of a web application as a WAR file and with Tomcat configured
+    not to unpack WARs will result in significantly slower startup times and
+    slower runtime performance. Start-up times have been measured between three
+    and ten times slower. Runtime impact will depend significantly on the
+    application structure.</p>
+    
+    
+<p>It is strongly recommended not to set <code>unpackWARs="false"</code> on
+    a Host or <code>unpackWAR="false"</code> on a Context. Below is a list of
+    common reasons for disabling unpacking and the recommended alternative for
+    Tomcat 8:</p>
+    
+    
+<ul>
+      
+<li>
+<i>Security (appBase is readOnly to Tomcat user)</i> - Deploy (as a
+      different user) an unpacked directory to the appBase rather than a WAR
+      file.</li>
+      
+<li>
+<i>Sharing an appBase between multiple hosts</i> - Deploy WAR files
+      to a common location and then use context.xml files to add the web
+      applications to the hosts as required. Note sharing an appBase between
+      multiple hosts is strongly discouraged in all circumstances.</li>
+      
+<li>
+<i>Off-line deployment</i> - As of Tomcat 8.0.21, Tomcat will detect
+      when a WAR has been updated while it is not running and, when next
+      started, remove the out of date expanded directory and deploy the updated
+      WAR file so simply use <code>unpackWAR="true"</code> and continue to
+      deploy WARs when Tomcat is not running.</li>
+    
+</ul>
+
   
 </div>
 </div>

Modified: tomcat/site/trunk/xdocs/migration-8.xml
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-8.xml?rev=1663787&r1=1663786&r2=1663787&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-8.xml (original)
+++ tomcat/site/trunk/xdocs/migration-8.xml Tue Mar  3 20:48:02 2015
@@ -204,6 +204,36 @@ of Apache Tomcat.</p>
 
   </subsection>
 
+  <subsection name="Deployment">
+
+    <p>Deployment of a web application as a WAR file and with Tomcat configured
+    not to unpack WARs will result in significantly slower startup times and
+    slower runtime performance. Start-up times have been measured between three
+    and ten times slower. Runtime impact will depend significantly on the
+    application structure.</p>
+    
+    <p>It is strongly recommended not to set <code>unpackWARs="false"</code> on
+    a Host or <code>unpackWAR="false"</code> on a Context. Below is a list of
+    common reasons for disabling unpacking and the recommended alternative for
+    Tomcat 8:</p>
+    
+    <ul>
+      <li><i>Security (appBase is readOnly to Tomcat user)</i> - Deploy (as a
+      different user) an unpacked directory to the appBase rather than a WAR
+      file.</li>
+      <li><i>Sharing an appBase between multiple hosts</i> - Deploy WAR files
+      to a common location and then use context.xml files to add the web
+      applications to the hosts as required. Note sharing an appBase between
+      multiple hosts is strongly discouraged in all circumstances.</li>
+      <li><i>Off-line deployment</i> - As of Tomcat 8.0.21, Tomcat will detect
+      when a WAR has been updated while it is not running and, when next
+      started, remove the out of date expanded directory and deploy the updated
+      WAR file so simply use <code>unpackWAR="true"</code> and continue to
+      deploy WARs when Tomcat is not running.</li>
+    </ul>
+
+  </subsection>
+
 </section>
 
 <section name="Upgrading 8.0.x">



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

Reply via email to