logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cakalic, James P." <James.Caka...@maritz.com>
Subject RE: Configuration in stateless objects?
Date Thu, 11 Jan 2001 00:38:17 GMT
As of version 0.8.5, "At the initialization of the Category class, the file
log4j.properties will now be searched from the search path used to load
classes. If the file can be found, then it is fed to the
PropertyConfigurator.configure(java.net.URL) method."

Best regards,
Jim Cakalic

> -----Original Message-----
> From: Kirk Benson [mailto:kirk.benson@brokat.com]
> Sent: Wednesday, January 10, 2001 8:28 AM
> To: LOG4J Users Mailing List
> Subject: Configuration in stateless objects?
> 
> 
> I have an implementation question:
> 
> We have lots of code (servlets, JSPs, EJBs) that execute within an
> application server as stateless client objects.  Therefore, 
> we have no easy
> access to the startup logic of the JVM from which to invoke the
> PropertyConfigurator.configure() method.  I think the right 
> way to do this
> is to define a subclass of Category (similar to MyCategory) 
> and implement a
> static block within this class to configure the system.  As 
> long as all
> logging uses this derived Category subclass, then the first call to
> getInstance() will configure the system.
> 
> Is there a better way to do this?
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-user-help@jakarta.apache.org
> 

Mime
View raw message