RE: log4j and Eclipse

2004-07-16 Thread James Stauffer
Try catch(Throwable e)

James Stauffer


-Original Message-
From: Bill Harrelson [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 16, 2004 2:52 PM
To: [EMAIL PROTECTED]
Subject: log4j and Eclipse


lI'm trying to get log4j running with Tomcat and Eclipse.

I have in my servlet init procedure:

Logger logger = Logger.getLogger(my.logger.name);

I have two webapps, w1 and w2, and a log4j.properties file in each 
/classes subdirectory, and the log4j jar in each /lib directory.

works fine running Tomcat stand-alone, but under Eclipse, when I 
step over the getLogger call, Eclipse never returns to my init 
procedure.  Subsequent statements are not executed, and no 
exception is thrown (and this is in a try/catch block for (Exception 
e)).

I have tried putting the jar in the Eclipse classpath explicitly, taking
them out, putting it in common/lib, and shared/lib, nothing seems to 
duplicate the behavior of stand-alone tomcat.  If I put the jar(s) in 
the Eclipse classpath explicitly, it seems to only have one repository 
context (as one might expect) and only one of the Loggers works.

Can anyone tell me what is happening and how to get around it?

Thanks,

Bill
-- 
William B. Harrelson
President
Accordare
27 Ashland Street, Arlington, MA 02476
t:781-646-2241 f:781-646-2242
[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: log4j and Eclipse

2004-07-16 Thread Bill Harrelson
Well, thanks (should have thought of that, - newbie mistake), that at 
least confirms that I was getting a class not found in one of the 
configurations.  So, I'm back to putting the jars in each /lib directory 
into the Eclipse debug classpath explicitly, now the first app finds 
the configuration and works fine, and the second app executes fine, 
just no log output is produced.

It works fine in Tomcat stand-alone.  Any ideas what to do?

Thanks,

Bill


Send reply to:  Log4J Users List [EMAIL PROTECTED]
From:   James Stauffer [EMAIL PROTECTED]
To: 'Log4J Users List' [EMAIL PROTECTED]
Subject:RE: log4j and Eclipse
Date sent:  Fri, 16 Jul 2004 14:55:02 -0500

 Try catch(Throwable e)
 
 James Stauffer
 
 
 -Original Message-
 From: Bill Harrelson [mailto:[EMAIL PROTECTED] 
 Sent: Friday, July 16, 2004 2:52 PM
 To: [EMAIL PROTECTED]
 Subject: log4j and Eclipse
 
 
 lI'm trying to get log4j running with Tomcat and Eclipse.
 
 I have in my servlet init procedure:
 
 Logger logger = Logger.getLogger(my.logger.name);
 
 I have two webapps, w1 and w2, and a log4j.properties file in each 
 /classes subdirectory, and the log4j jar in each /lib directory.
 
 works fine running Tomcat stand-alone, but under Eclipse, when I 
 step over the getLogger call, Eclipse never returns to my init 
 procedure.  Subsequent statements are not executed, and no 
 exception is thrown (and this is in a try/catch block for (Exception 
 e)).
 
 I have tried putting the jar in the Eclipse classpath explicitly, taking
 them out, putting it in common/lib, and shared/lib, nothing seems to 
 duplicate the behavior of stand-alone tomcat.  If I put the jar(s) in 
 the Eclipse classpath explicitly, it seems to only have one repository 
 context (as one might expect) and only one of the Loggers works.
 
 Can anyone tell me what is happening and how to get around it?
 
 Thanks,
 
 Bill
 -- 
 William B. Harrelson
 President
 Accordare
 27 Ashland Street, Arlington, MA 02476
 t:781-646-2241 f:781-646-2242
 [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

-- 
William B. Harrelson
President
Accordare
27 Ashland Street, Arlington, MA 02476
t:781-646-2241 f:781-646-2242
[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]