Re: log4j.xml problem

2012-09-26 Thread Douglas E Wegscheid
that is correct. you should only see WARN on up. I verified it: this only logs the WARN when run against your log4j.xml. import org.apache.log4j.Logger; public class L { public static void main (String[] args) { Logger logger = Logger.getLogger(L.class); logger.info("info"); logger.

Re: log4j.xml problem

2012-09-26 Thread Oliver Ruebenacker
Hello, On Wed, Sep 26, 2012 at 2:46 PM, Douglas E Wegscheid wrote: > at least one problem higher in the file (lines 27 and 31): too many XML > comment closes (-->) Thanks! That made the parse error messages disappear. Unfortunately, the file still seems to have no effect. Let me che

Re: log4j.xml problem

2012-09-26 Thread Douglas E Wegscheid
at least one problem higher in the file (lines 27 and 31): too many XML comment closes (-->) --> --> good XML editor is recommended ■ DOUGLAS E. WEGSCHEID // LEAD ENGINEER (269) 923-5278 // douglas_e_wegsch...@whirlpool.com "A wrong note played hesitatingly is a wrong note. A wr

Re: log4j.xml problem

2012-09-26 Thread Oliver Ruebenacker
Hello, Oops, sorry, I attached the wrong file. Attached is the right one. Thanks! Take care Oliver On Wed, Sep 26, 2012 at 12:44 PM, Douglas E Wegscheid wrote: > be willing to look at it, but it looks like you attached your web.xml > instead of the log4j.xml > ■ DOUGLAS

Re: log4j.xml problem

2012-09-26 Thread Douglas E Wegscheid
be willing to look at it, but it looks like you attached your web.xml instead of the log4j.xml ■ DOUGLAS E. WEGSCHEID // LEAD ENGINEER (269) 923-5278 // douglas_e_wegsch...@whirlpool.com "A wrong note played hesitatingly is a wrong note. A wrong note played with conviction is interpretation."

RE: log4j.xml

2008-08-07 Thread Scott Deboy
There is a sample receiver configuration available from the Welcome tab in Chainsaw - there's an example receiver configuration xml file available from a button on the tab's toolbar. Copy and modify that example configuration file to some place on your file system and modify the application-wide p

Re: log4j.xml location issue

2007-09-04 Thread Jacob Kjome
At 12:04 PM 9/4/2007, you wrote: > >Hello, > >I have the files commons-logging.properties, log4j.dtd and log4j.xml >in the root of my eclipse proyect. If I create a jar file with them >inside, all the log works properly. But I don´t want to have that >files inside a jar. > >Can anyone tell me how

Re: log4j.xml vs. log4j.properties in Jbuilder 2006

2007-05-18 Thread Jacob Kjome
The warning you are seeing is for Tomcat's logging. I'm not sure how JBuilder manipulates the classloading behavior of Tomcat when it is embedded, but normally the way that you configure Tomcat to use Log4j for logging is to put log4j.jar and commons-logging.jar in Tomcat's common/lib direct

RE: log4j.xml vs log4j.properties

2006-02-06 Thread Bender Heri
xml is the newer development. I read once that sometimes in the future only xml will be supported. In either case, it has more possibilities, like filters. Annother point is that the autoconfiguration searches first for a xml file in the classpath, and only if it is not found it looks for a prop

Re: log4j.xml validation

2005-12-13 Thread Curt Arnold
Dirk Ooms wrote: And what about the log4j.dtd which is still in the 1.3alpha6 distribution? Has it any value? Some, but it would only catch a small set of errors (misspelling appender for example), but would not catch bad class names, bad file values, missing attributes, etc. --

Re: log4j.xml validation

2005-12-13 Thread Dirk Ooms
And what about the log4j.dtd which is still in the 1.3alpha6 distribution? Has it any value? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: log4j.xml validation

2005-12-12 Thread Curt Arnold
Dirk Ooms wrote: Hi, i am a bit puzzled on how i should do an apriori validation of a log4j.xml in log4j1.3 (without applying it to a LoggerRepository). The XML format used by log4j was not designed so that it can be effectively validated using standard XML validation technologies. It

RE: log4j.xml

2004-01-21 Thread Shapira, Yoav
Howdy, >Should I actually create each logger as a java class and reference this >in my code? No. For example: import org.apache.log4j.Logger; class MyClass { private static final Logger LOGGER = Logger.getLogger(MyClass.class); void myMethod() { LOGGER.debug("Entering myMethod.");

RE: log4j.xml

2004-01-21 Thread Joe Collins
-Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 21 January 2004 18:02 To: Log4J Users List Subject: RE: log4j.xml Howdy, You want log4j.xml on the classpath for automatic initialization? If so, server/lib is not good, as only jars from there get added. Is there a server

RE: log4j.xml

2004-01-21 Thread Shapira, Yoav
Howdy, You want log4j.xml on the classpath for automatic initialization? If so, server/lib is not good, as only jars from there get added. Is there a server/classes directory? If so, put log4j.xml there. As an aside, your code snippet could look better: import the Logger class, don't use the FQ