Ah, well, that ties in perfectly with the conversation being held in this
thread <gr>. Thanks for the explanation.
----- Original Message -----
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 26, 2001 1:04 AM
Subject: Re: [JBoss-user] log4j system.out category
> Because System.out.println statements are not sent to all appenders when
> one uses org.apache.log4j.ConsoleAppender. It that is fine for you good.
> Its not fine for me.
>
>
> xxxxxxxxxxxxxxxxxxxxxxxx
> Scott Stark
> Chief Technology Officer
> JBoss Group, LLC
> xxxxxxxxxxxxxxxxxxxxxxxx
> ----- Original Message -----
> From: "Guy Rouillier" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, September 25, 2001 8:28 PM
> Subject: Re: [JBoss-user] log4j system.out category
>
>
> > Why does JBoss use its own classes when the ones that come with log4j
work
> > just as well? I was learning to use log4j for my own (non-JBoss) Java
> > programs. I started with the JBoss log4j.properties file, and when I
got
> > various "class not found" messages, I replaced the JBoss classes with
the
> > standard log4j ones as follows:
> >
> > # log4j.categoryFactory=org.apache.log4j.DefaultCategoryFactory
> > log4j.appender.Console=org.apache.log4j.ConsoleAppender
> >
> > I don't really remember now why the categoryFactory line is commented
> out -
> > maybe that class is abstract. Regardless, this configuration works just
> > fine.
> >
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
