DO NOT REPLY [Bug 35774] New: - TCCL problem in J2EE Container

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35774>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35774

           Summary: TCCL problem in J2EE Container
           Product: Commons
           Version: 1.0.4
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Logging
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: michael.kopp@gmx.at


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.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org