RE: Problems with my classpath?

2004-03-26 Thread Jacob Kjome
Hi Yoav, At 09:03 AM 3/26/2004 -0500, you wrote: Hi, Not quite. I normally would let this go, but this is such an important issue and we see so many problems related to it ;) Additions interspersed. >ClassNotFoundException means that you were trying to dynamically load a >class at runtime using

RE: Problems with my classpath?

2004-03-26 Thread Eliezer Chavez
Thanks Yoav I have solved my issue with this really helpfull explanation Regards, Eliezer E Chavez Gcia. Sistemas Riesgo y Workflow V.P. Administracion de Datos Banco de Venezuela - Grupo Santander Telf. +58-(212)-5012480 mail. [EMAIL PROTECTED]

RE: Problems with my classpath?

2004-03-26 Thread Andy McBride
Try: export CLASSPATH= Note the = Regards Andy > -Original Message- > From: Eliezer Chavez [mailto:[EMAIL PROTECTED] > Sent: 25 March 2004 07:36 > To: [EMAIL PROTECTED] > Subject: Problems with my classpath? > > > When i run my application with > java -classpath runs well > > Bu

Syslog -t issue

2004-03-26 Thread Rajkumar, Haripriya (Haripriya)
Hello, I am having problems seeing the log messages on UNIX syslog file. The problem occurs only when syslogd is started with -t option.(this option turns off syslogd from listening on UDP port) If syslogd is started without this option I am able to see the messages? Does the SyslogAppender have

RE: Problems with my classpath?

2004-03-26 Thread Shapira, Yoav
Hi, Not quite. I normally would let this go, but this is such an important issue and we see so many problems related to it ;) Additions interspersed. >ClassNotFoundException means that you were trying to dynamically load a >class at runtime using something like >Class.forName("com.mycompany.MyC

AW: Using my own ThreadGroupRenderer

2004-03-26 Thread Extern.Otto
Hello! I still have the problem with use of org.apache.log4j.or.ThreadGroupRenderer. I the javadoc to the class I found that there is: "No usage of org.apache.log4j.or.ThreadGroupRenderer" What is the meaning of ThreadGroupRenderer when it is not used in Log4j? My own extension is ignored, too.

Re: log4j and tomcat 3.2 - reloadable context

2004-03-26 Thread Eliot Sykes
I WISH we could upgrade to tomcat 5, but that's something penned for the future. Good news is I have got a solution to the problem. By using log4j's default initialisation procedure of putting log4j.properties in the classpath, everything is working as needed now. Upon recompile, the log4j set