Sure that's possible - just study the Log4J Javadoc. I think you could either extend 
one of the existing Configurator classes or roll your own if you want to do something 
really novel. 
As far as extending is concerned: I don't know about the XML configuration, but it 
should not be a problem to store your Log4J config in a database, fill a Properties 
object with the entries from the database and then pass the Properties object to the 
PropertiesConfigurator.

Torben

---
Torben Fruechtenicht
Developer
IT Solutions

UBIS AG                fon:   +49 30 39929-731
Dircksenstra�e 42-44   fax:   +49 30 39929-900
D-10178 Berlin         email: [EMAIL PROTECTED]
Germany                web:   http://www.ubis-ag.com
--- 

> -----Urspr�ngliche Nachricht-----
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 10. Juli 2003 14:20
> An: [EMAIL PROTECTED]
> Betreff: configuring log4j without a file? is it possible? 
> 
> 
> Hello people,
> 
> In the examples people use they all seem to give the path of 
> a config file
> to configure log4j.
> Is there anyway we can configure log4j (before it logs to a appender)
> without giving it the path of a config file???
> maybe get config from Database? another machine etc?
> any ideas? solutions? i would be extremely grateful
> 
> Cheers.
> 
> ______________________________________________________________
> _________________
>  The information transmitted is intended only for the person 
> or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Statements and opinions expressed in this e-mail may not
> represent those of the company. Any review, retransmission, 
> dissemination
> or other use of, or taking of any action in reliance upon, 
> this information
> by persons or entities other than the intended recipient is 
> prohibited. If
> you received this in error, please contact the sender immediately and
> delete the material from any computer. This e-mail may be read by an
> employee of the company as part of the internal monitoring 
> process and is
> therefore not to be considered private by the sender or the recipient.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to