commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Libbrecht <>
Subject Re: commons-logging unsuited for cross-context webapplication invocation usage - migrating to slf4j?
Date Tue, 21 Apr 2009 22:22:52 GMT
this is the type of comments I had heard several times about commons- 
logging... classloader issue...
I never understood them, what you describe is a probably hypothesis.


Le 22-avr.-09 à 00:03, John Bollinger a écrit :

> I confess that I don't understand the portal environment very well,  
> but if I'm following this correctly then PLUTO-553 is a symptom of a  
> more fundamental issue: objects in a Pluto portlet cannot rely on  
> the context classloader to be the correct one from which to obtain  
> resources.  This arises because -- as I understand it -- Pluto  
> provides portlet isolation analogous to the isolation of distinct
> webapps in a servlet container, but unlike a servlet container, it
> allows one portlet to invoke methods on the live objects of another,  
> not changing the context classloader when such cross-context method  
> invocations occur.
> If I have analyzed that correctly then I would account it a Pluto  
> bug, not a JCL bug.

View raw message