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 22:11:32 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 ceki@apache.org  2005-01-27 23:11 -------
I thought you had made a simple typo, hence my question "you mean point (2)?". 
Otherwise, the follwing two paragraphs do not make sense (to me).

 The discovery mechanism for commons-logging currently overlooks/assumes two points:
 1. That the thread-context class loader is a child who's parent hierarchy
 includes the commons-logging.jar.
 2. That the ClassLoaders in the current hierarchy exhibit the default
 parent-first behavior.

 Correction... my guess is that JUnit/Cactus are in conflict with point (1). 
 That a thread context classloader is being set up that does not defer up a
 hierarchy that includes the commons logging code.

I think in the second paragraph you meant to say:

 Correction... my guess is that JUnit/Cactus are in conflict with point (2). 

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