Howdy, I could rant on this issue for a long time, but I'll stick to three points.
>Thanks for the advice. I tried using Log4J directly by one of my classes >and, like you said, it worked. Ahh, good, a simple setup that works. >However, I wanted to stick with commons >logging since this is (supposedly) the most flexible logging solution. Thank you for providing something funny in today's boring batch of emails to this list. ;) Yes, let's take something simple that works and replace it with something complicated that may or may not work after some fidgeting and trial and error. >However, I am surprised that this was all necessary. I am also surprised >that it is (I think) undocumented. Undocumented? Search this and the log4j-user list's archives for many many many other people who've run into the same problems as you, and worse. You'll find many solutions, workaround, and black magic. And yes, I do consider the list archives as part of the documentation ;) 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
