[
https://issues.apache.org/jira/browse/LOGGING-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed LOGGING-73.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
According to Simon this was fixed in 1.1.0.
> [logging] TCCL problem in J2EE Container
> ----------------------------------------
>
> Key: LOGGING-73
> URL: https://issues.apache.org/jira/browse/LOGGING-73
> Project: Commons Logging
> Issue Type: Bug
> Affects Versions: 1.0.4
> Environment: Operating System: other
> Platform: Other
> Reporter: Michael Kopp
> Fix For: 1.1.0
>
> Attachments: LogFactoryImpl.java
>
>
> Everybody that uses commons-logging in an J2EE Container (especially jboss)
> has
> problems when the TCCL is not the same as the current ClassLoader. The
> solution
> cannot be to drop the commons-logging.jar out of the ear/war file, as it would
> prevent to have an application specific logging instance.
> Commons-logging preferes the TCCL which is OK. But if it finds a Logger in the
> TCCL that does not fit to the current Log interface it throws an error instead
> of trying the current CL.
> I propose to change this. I will attach a changed LogFactoryImpl.java. The
> changed factory still prefers TCCL, but will try the current class loader if
> the
> LOG_INTERFACE is not assignable for the class found via TCCL.
> It allows us to run more painlessly in an J2EE Container and to keep
> commons-logging class loader preferences.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
