commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28291] - [logging] ContextClassLoader may load Log impl from wrong context in JDK 1.4
Date Thu, 27 Jan 2005 23:00:15 GMT
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=28291>.
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=28291





------- Additional Comments From rsitze@apache.org  2005-01-28 00:00 -------
Either point will break JCL.  My assumption is irrelevant in the end.

I'm simply asking the defect owner to help identify *which* one might be 
working here.

If the "thread context classloader" is adhering to the "parent first" search 
behavior, then this would only be a problem if the "thread context 
classloader" did not have the "current class's classloader" in it's hierarchy.

If the "thread context classloader" is adhering to the "child first" search 
behavior, then it opens up all sorts of ugly doors in a test environment, so 
I'm guessing this isn't true.

-- 
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


Mime
View raw message