Prior to release 1.0.4, none of the standard Log implementations were - Serializable. If you are using such a release and have a Serializable classe + Serializable. If you are using such a release and have a Serializable class with a member that is of type Log then it is necessary to declare that member to be transient and to ensure that the value is restored on deserialization. The recommended approach is to define a custom diff --git a/xdocs/tech.xml b/xdocs/tech.xml index 6b0e42b..4296739 100644 --- a/xdocs/tech.xml +++ b/xdocs/tech.xml @@ -173,12 +173,12 @@ This guide is aimed at describing the technologies that JCL developers and expert users (and users who need to become experts) should be familiar with. The aim is to give an understanding whilst being precise but brief. - Details which are not relevent for JCL have been suppressed. + Details which are not relevant for JCL have been suppressed. References have been included.
- These topics are a little difficult and it's easy for even experience developers to make - mistakea. We need you to help us get it right! Please submit corrections, comments, additional references + These topics are a little difficult and it's easy for even experienced developers to make + mistakes. We need you to help us get it right! Please submit corrections, comments, additional references and requests for clarification by either:
@@ -356,7 +356,7 @@ VMSpec The Java Virtual Machine Specification, Second EditionNote: the term child-first (though commonly used) is misleading. A better term (and one which may be encountered on the mailing list) is parent-last. - This more accurately describes the actual process of classloader performed + This more accurately describes the actual process of classloading performed by such a classloader.
@@ -448,14 +448,14 @@
Thread.setContextClassLoader emphasizes the setting of the
context classloader as an aspect of thread creation. However, in many
applications the context classloader is not fixed at thread creation but
- rather is changed throughout the life of thread as thread execution moves
+ rather is changed throughout the life of a thread as thread execution moves
from one context to another. This usage of the context classloader is
particularly important in container applications.
For example, in a hypothetical servlet container, a pool of threads is created to handle HTTP requests. When created these threads have their - context classloader set to a classloader that loads container classes. + context classloader set to a classloader that loads container classes. After the thread is assigned to handle a request, container code parses the request and then determines which of the deployed web applications should handle it. Only when the container is about to call code associated diff --git a/xdocs/troubleshooting.xml b/xdocs/troubleshooting.xml index f97dbdf..869cbb0 100644 --- a/xdocs/troubleshooting.xml +++ b/xdocs/troubleshooting.xml @@ -37,8 +37,8 @@
Diagnostics is a feature introduced in JCL 1.1 as an aid to debugging problems
with JCL configurations. When diagnostics are switched on, messages are logged
-to a stream (specified by the user) by the two main class involved in discovery
-JCL (LogFactory and LogFactoryImpl).
+to a stream (specified by the user) by the two main classes involved in discovery
+in JCL (LogFactory and LogFactoryImpl).
Diagnostics are intended to be used in conjunction with the source. The source
@@ -74,7 +74,7 @@ These are of the form:
The system identity hash code is found by calling System.identityHashCode()
which should uniquely identify a particular instance. The classname is usually the fully qualified
class name though in a few cases, org.apache.commons.logging.impl.LogFactoryImpl may be
-shorten to LogFactoryImpl to increase ease of reading. For example:
+shortened to LogFactoryImpl to increase ease of reading. For example:
sun.misc.Launcher$AppClassLoader@20120943
@@ -176,11 +176,11 @@ Before assigning a Log instance, LogFactory loads a
for each diagnostic message logged by this process.
-The implementation used can vary per Thread context classloader (TCCL). If this the first time
+The implementation used can vary per Thread context classloader (TCCL). If this is the first time
that a Log has been requested for a particular TCCL a new instance will be created.
-Information of particular interest is logged at this stage. Details of the TCCL are logging
+Information of particular interest is logged at this stage. Details of the TCCL are logged
allowing the OID later to be cross-referenced to the toString value
and the classloader tree. For example, the
following log snippet details the TCCL (lines split):
@@ -282,7 +282,7 @@ of other containers using a custom implementation.
the two LogFactory Class instances are not equal and so the cast must fail.
-The policy adopted by JCL in this situation is to re-throw this exception. Addition information
+The policy adopted by JCL in this situation is to re-throw this exception. Additional information
is included in the message to help diagnosis. The reasoning behind this choice is that a
particular LogFactory implementation has been actively specified and this
choice should not be ignored. This policy has unfortunate consequences when running in
@@ -316,7 +316,7 @@ implementation.
the most modern release
- Replace the commons-logging jar in the application with the commons-logging-adapter jar.
+ Replace the commons-logging jar in the application with the commons-logging-adapters jar.
This will ensure that application classloader will delegate to it's parent when loading
LogFactory.