Siphalor/tweed5-commons-logging
1
0
Fork 0
Code Activity

Changes because of the TLP move.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/logging/trunk@560818 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Dennis Lundberg
2007-07-29 21:02:06 +00:00
parent beab13d1b8
commit d6bc112b79
18 changed files with 83 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
xdocs/troubleshooting.xml
View File

@@ -301,7 +301,7 @@ classloader used to load <code>LogFactory</code> and to the TCCL.
<li>WebSphere Application Server (other versions).</li>
</ul>
<p>
The Jakarta Commons team would be grateful if reports were posted to the development list
The Apache Commons team would be grateful if reports were posted to the development list
of other containers using a custom implementation.
</p>
<subsection name='The Incompatible LogFactory Issue'>
@@ -315,10 +315,10 @@ of other containers using a custom implementation.
implementation should be used but Class 'com.ibm.ws.commons.logging.TrLogFactory' cannot be converted
to 'org.apache.commons.logging.LogFactory'. The conflict is caused by the presence of multiple
LogFactory classes in incompatible classloaders. Background can be found in
http://jakarta.apache.org/commons/logging/tech.html. If you have not explicitly specified a custom
http://commons.apache.org/logging/tech.html. If you have not explicitly specified a custom
LogFactory then it is likely that the container has set one without your knowledge.
In this case, consider using the commons-logging-adapters.jar file or specifying the standard
LogFactory from the command line. Help can be found @http://jakarta.apache.org/commons/logging.
LogFactory from the command line. Help can be found @http://commons.apache.org/logging.
</pre></code>
<p>
This is a WebSphere example so the name of the custom LogFactory is