Hi, >a little policy-question here: >i'm using log4j-configuration exactly that way (calling >BasicConfigurator.configure() and then >XMLConfigurator to read the config file) to ensure that logging is at >least configured and in case something goes wrong with the config >file (not found, for example) i can log a fatal message.
I didn't mean to suggest the above was always wrong. I was only proposing it as one reason why the original poster might be having the difficulties he/she was reporting. ;) But since we're on the topic, I don't think the above is necessarily a bad approach. By nature, I tend to really constrain the environment I'm developing in: I make sure the config file is there and correct, proper permissions set, and I know exactly which code will execute first in the JVM and initialize log4j. Accordingly, I only configure it once and it's worked for me. But if you don't have a tight control over the environment, and as a backup policy, the BasicConfigurator approach is not bad IMHO. Yoav Shapira Millennium ChemInformatics
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: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
