On Apr 21, 2009, at 5:39 PM, Jochen Wiedmann wrote:
The thing is that there is something like a "common" ClassLoader in Pluto (and, most possibly, in all Portlet servers). But that is nothing special: We know that from Tomcat as well. (Of course, the common ClassLoader isn't endorsed by the Servlet specification, but we all know that it is a necessity.) Now, if we start using the various class loaders, we'll have class loading issues with JCL. (Most of them, because people don't understand the concept.) But you can be sure (and that's where I absolutely disagree with PLUTO-533), that you can have class loading issues with SFL4J as well: Of course, I won't have any, if there is a single binding in a shared class loader. But that's mainly the case because SFL4J is currently less common than JCL. In other words, as soon as SFL4J bindings will start to be part of any major or minor component, they will start to override each other, causing all kind of trouble.
I'm not sure what you mean by "SLF4J bindings will start to be part of any major or minor component" and I think I've seen you make that comment before. Can you provide an example of how you think that will occur?
I agree that class loading issues with SFL4J will be simpler (because it's architecture in that aspect is much simpler), but nothing more.
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
