On Sun, Feb 16, 2003 at 03:25:14PM +0200, Zeev B wrote:
> The Log4j javadocs state that calling the configure method will not effect
> the current configuration (to do that you should call the resetConfiguration
> method first).

That's interesting! I didn't know that :) This way we could have the
application specific logging configuration separated from JBoss. Thanks
:)

//Anders

> ----- Original Message -----
> From: "Anders Engstr�m" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, February 14, 2003 4:49 PM
> Subject: Re: [JBoss-user] JBoss & Log4J
> 
> 
> On Fri, Feb 14, 2003 at 10:17:22AM +0200, Alexopoulos Dimitris
> ([EMAIL PROTECTED]) wrote:
> > Hello All!
> >
> > Couldn't you create a class that instantiates a Log4j Logger of your own?
> > This way you could use log4j's method
> >
> > PropertyConfigurator.configure("pathToYourLog4jConfigFile");
> >
> > and read always your configuration. Is it necessary to use the JBoss
> logger?
> > Excuse me if I have misunderstood something... ;-)
> >
> 
> That would result in your configuration (pathToYourLog4jConfigFile)
> replacing the JBoss one - and every other previously configured loggers
> initiated from other deployed applications.
> 
> //Anders


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to