Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 16707 invoked from network); 1 Sep 2003 17:37:49 -0000 Received: from unknown (HELO minotaur.apache.org) (209.237.227.194) by daedalus.apache.org with SMTP; 1 Sep 2003 17:37:49 -0000 Received: (qmail 36278 invoked from network); 1 Sep 2003 17:37:40 -0000 Received: from unknown (HELO jboss.org) (127.0.0.1) by localhost with SMTP; 1 Sep 2003 17:37:40 -0000 Message-ID: <3F5383E2.8050904@jboss.org> Date: Mon, 01 Sep 2003 19:37:38 +0200 From: Remy Maucherat User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Problem switching to Struts 1.1 References: <018f01c370ad$856b4a00$0302a8c0@jemoserver> In-Reply-To: <018f01c370ad$856b4a00$0302a8c0@jemoserver> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Marco Tedone wrote: > Hi, I posted this issue to the struts-user list 3 times, but noone replied > to me and frankly I'm beginning to be a little worried. In few words we have > an application which was running fine until struts rc1 but when we switched > to Struts 1.1 the following exceptions is thrown: > > > The problem seems to be the org.apache.commons.logging.impl.Log4jCategoryLog > class which is not found in the classpath. Now, I had a look at the > commons-logging file and actually there is a similar class called > org.apache.commons.logging.impl.Log4JCategoryLog (please note the capital > 'J'). What shall I do then? Yes, something looks very fishy regarding case sensitivity with the log4j support in commons-logging. You might want to file a bug against commons-logging and because class naming is inconsistent, and can cause user errors (for example, there's a o.a.c.l.impl.Log4jFactory class along with a o.a.c.l.impl.Log4JLogger class). That being said, I've only seen that error occur if the webapp is privileged (ie, there's a Context element with a privileged="true" attribute). If you don't know what privileged does, and put it there because it sounds better, I suggest you remove it (and read the docs) :) Remy