Reinhard Pötz wrote:
I'm sorry, I forgot to respond earlier. Find my comments inline.
No problem, thanks for responding.
I don't understand... if the wrapper web application depends on
commons-logging and makes arrangements to load the commons-logging
jar into the classpath it should clash when I attempt to load the
jcl-over-slf4j jar file
not necessarily, though I'm not sure what exactly is happening. My
guess: When the reloading classloader is used, most of the libraries
are loaded by a separate classloader (-> the reloading classloader)
than the context classloader. The context classloader only loads the
libraries that are necessary to use the reloading classloader itself.
I suspect you're right.
For the moment at least, I now have slf4j working and am using LogBack
in all new code. I was a little worried that it was just luck that the
classloader decided to use the 'correct' jar file. I thought maybe the
loading order might change with the addition of new code at any time and
randomly stop the app working... but I'm happier that that won't happen now.
Thanks again for pointing out the 'mvn dependency:tree' command...
that's a very useful one to know. I'm feeling a lot more comfortable
using Maven now that I've read up on exclusions and transitive dependencies.
Regards,
David Legg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
