DO NOT REPLY [Bug 34661] - [logging][PATCH] Improvements to LogFactoryImpl

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

DO NOT REPLY [Bug 34661] - [logging][PATCH] Improvements to LogFactoryImpl

Bugzilla from bugzilla@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=34661>.
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=34661





------- Additional Comments From [hidden email]  2005-06-02 07:56 -------
Created an attachment (id=15259)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=15259&action=view)
diff to LogFactoryImpl rev 5b

Patch to LogFactoryImpl in trunk, following recent commit of patch 5a -- thanks
Simon :)

Description of the patch is as per comment #9 above.

Had a chance to think about why case Robert's 24 succeeds with this patch
applied, and it is as expected.  Case 20 and 24 both have the caller in the
parent loader with the TCCL set to the child.  In both cases JCL is in both the
parent and child.  In 20 Log4j is in the child; in 24 it is in both parent and
child. Initial discovery fails in both cases because the Log discovered by the
TCCL is incompatible with the LogFactory bound to the caller.  Case 24 succeeds
with this patch because when an attempt is made to load Log4jLogger using the
parent loader, log4j.jar is visible to the parent loader, so discovery
succeeds.

--
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: [hidden email]
For additional commands, e-mail: [hidden email]