Re: Commons Logging Issues

On Thu, 07 Aug 2003 15:33:50 +1000, Scott Farquhar wrote:

> We are having problems deploying JIRA in the latest versions of Tomcat due
> to commons logging hell.  It seems that Tomcat packages commons-logging in
> servlet/lib/ which clashes if you package your own version.
> 
> Of course I need to package my own version of commons-logging because if I
> deploy on any other server I need it.
> 
> Here is a good article about it:
> 
>    http://www.qos.ch/logging/thinkAgain.html
> 
> Our specific problem is here:
> 
>    http://marc.theaimsgroup.com/?l=tomcat-dev&m=103481398706987&w=2
> 
> Now, my question is - do we actually benefit from using commons-logging
> instead of log4j?  What were the reasons for it?  Are they still valid?

The problem will not go away ... unfortuatly. Classloader hell is dll hell
for java. Something like jboss just causes you more pain because of it's
"wonderfully helpfull" classloader. I had a nightmare getting log4j to
work in OSUser when I had OSUser and another application that used log4j
in seperate ears (OSUser was compiled against an older or newer version I
can't remeber which). 

At least with commons logging I can switch to jdk 1.4 logging (system
properties) and know that the classes are in the boot classloader and I'm
not going to get conflicts. 

> Cheers,
> Scott




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01