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.
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
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
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
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."
