logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: calling DOMConfigurator.configureAndWatch() 2 times
Date Wed, 13 Aug 2003 13:52:41 GMT


>Also, it is programmatically possible to check if Log4j has been
>previously, thus avoiding the problem (which may or may not help in
>particular case).  My development team creates components used
>our enterprise, and if an application has configured Log4j, we want to
>configuring it ourselves and instead piggy-back off their

This is a good habit: we do the same thing.

>The code to check if Log4j has been configured follows:
>public static boolean isConfigured() {

This code is also on the log4j wiki pages as it's a FAQ.  Note that it's
not guaranteed to be 100% effective, i.e. it might return false
positives or negatives.  I haven't run across such a case yet, but it's
a CYA statement.

Yoav Shapira

This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.

To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org

View raw message