Author: kkolinko
Date: Wed Mar 9 02:03:38 2011
New Revision: 1079640
URL: http://svn.apache.org/viewvc?rev=1079640&view=rev
Log:
In the Migration Guide for 5.5 > 6.0 migration,
Provide more details on the logging package being renamed.
Explicitly mention commons-logging.jar is a separate section.
Modified:
tomcat/site/trunk/docs/migration.html
tomcat/site/trunk/xdocs/migration.xml
Modified: tomcat/site/trunk/docs/migration.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration.html?rev=1079640&r1=1079639&r2=1079640&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration.html (original)
+++ tomcat/site/trunk/docs/migration.html Wed Mar 9 02:03:38 2011
@@ -224,7 +224,10 @@
<a href="#Modified_classloading">Modified classloading</a>
</li>
<li>
-<a href="#Logging_API_package_renaming">Logging API package renaming</a>
+<a href="#Internal_Logging_API_package_renaming">Internal Logging API package
renaming</a>
+</li>
+<li>
+<a href="#commons-logging.jar">commons-logging.jar</a>
</li>
<li>
<a href="#SSLEnabled_attribute_on_Connector">SSLEnabled attribute on
Connector</a>
@@ -567,11 +570,11 @@ problems.</p>
<tr>
<td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
-<a name="Logging API package renaming">
+<a name="Internal Logging API package renaming">
<!--()-->
</a>
-<a name="Logging_API_package_renaming">
-<strong>Logging API package renaming</strong>
+<a name="Internal_Logging_API_package_renaming">
+<strong>Internal Logging API package renaming</strong>
</a>
</font>
</td>
@@ -580,16 +583,57 @@ problems.</p>
<td>
<blockquote>
- <p>Commons-logging was package renamed to
<code>org.apache.juli.logging</code>
- so that application logging can be as independent as possible from the
- container, while still having the possibility of being unified. This
change is
- transparent when using java.logging, but requires compilation of the extra
- components when using log4j for Tomcat's logging. See the logging and
extras
+ <p>Apache Tomcat 5.5.x relied on the
+ <a href="http://commons.apache.org/logging/";>Apache Commons Logging</a>
+ library for its internal logging. Apache Tomcat 6.0.x and later no more
+ uses the library directly, but uses a private copy of it. The classes are
+ in the <code>org.apache.juli.logging</code> package.
+ </p>
+
+ <p>The rationale behind this change is that so that application logging
+ can be as independent as possible from the container, while still having
+ the possibility of being unified.</p>
+
+ <p>By default only a subset of Apache Commons Logging classes that are
+ needed to perform logging to <code>java.util.logging</code> is included
+ with Tomcat. If you want to configure Tomcat to redirect its logging into
+ <a href="http://logging.apache.org/log4j/";>Log4J</a>, or any other logging
+ framework supported by the full Apache Commons Logging library, you will
+ have to replace one of Tomcat JARs with the full implementation. The JAR
+ is available as an extras component. See the logging and extras
documentation for more details.</p>
- <p>The <code>commons-logging-api.jar</code> library is no longer provided
- by Tomcat. The web applications have to provide their own copy of that
- library, if needed</p>
+ </blockquote>
+</td>
+</tr>
+<tr>
+<td>
+<br/>
+</td>
+</tr>
+</table>
+
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+<tr>
+<td bgcolor="#828DA6">
+<font color="#ffffff" face="arial,helvetica,sanserif">
+<a name="commons-logging.jar">
+<strong>commons-logging.jar</strong>
+</a>
+</font>
+</td>
+</tr>
+<tr>
+<td>
+<blockquote>
+
+ <p>As Apache Tomcat no longer directly uses the
+ <a href="http://commons.apache.org/logging/";>Apache Commons Logging</a>
+ library, the <code>commons-logging-api.jar</code> library is no longer
+ provided for the web applications. The web applications that use
+ Apache Commons Logging have to provide their own copy of that library.
+ It is recommended to put it into their <code>WEB-INF/lib</code> directory,
+ like any other JAR.</p>
</blockquote>
</td>
Modified: tomcat/site/trunk/xdocs/migration.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration.xml?rev=1079640&r1=1079639&r2=1079640&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration.xml (original)
+++ tomcat/site/trunk/xdocs/migration.xml Wed Mar 9 02:03:38 2011
@@ -108,18 +108,39 @@ problems.</p>
</subsection>
- <subsection name="Logging API package renaming">
+ <subsection name="Internal Logging API package renaming">
- <p>Commons-logging was package renamed to
<code>org.apache.juli.logging</code>
- so that application logging can be as independent as possible from the
- container, while still having the possibility of being unified. This
change is
- transparent when using java.logging, but requires compilation of the extra
- components when using log4j for Tomcat's logging. See the logging and
extras
+ <p>Apache Tomcat 5.5.x relied on the
+ <a href="http://commons.apache.org/logging/";>Apache Commons Logging</a>
+ library for its internal logging. Apache Tomcat 6.0.x and later no more
+ uses the library directly, but uses a private copy of it. The classes are
+ in the <code>org.apache.juli.logging</code> package.
+ </p>
+
+ <p>The rationale behind this change is that so that application logging
+ can be as independent as possible from the container, while still having
+ the possibility of being unified.</p>
+
+ <p>By default only a subset of Apache Commons Logging classes that are
+ needed to perform logging to <code>java.util.logging</code> is included
+ with Tomcat. If you want to configure Tomcat to redirect its logging into
+ <a href="http://logging.apache.org/log4j/";>Log4J</a>, or any other logging
+ framework supported by the full Apache Commons Logging library, you will
+ have to replace one of Tomcat JARs with the full implementation. The JAR
+ is available as an extras component. See the logging and extras
documentation for more details.</p>
- <p>The <code>commons-logging-api.jar</code> library is no longer provided
- by Tomcat. The web applications have to provide their own copy of that
- library, if needed</p>
+ </subsection>
+
+ <subsection name="commons-logging.jar">
+
+ <p>As Apache Tomcat no longer directly uses the
+ <a href="http://commons.apache.org/logging/";>Apache Commons Logging</a>
+ library, the <code>commons-logging-api.jar</code> library is no longer
+ provided for the web applications. The web applications that use
+ Apache Commons Logging have to provide their own copy of that library.
+ It is recommended to put it into their <code>WEB-INF/lib</code> directory,
+ like any other JAR.</p>
</subsection>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
