Absolutely right Ceki. Think about using log4j in an application server.
No way should a general logging framework attempt to take down a VM.
----- Original Message -----
From: "Ceki Gülcü" <[EMAIL PROTECTED]>
To: "LOG4J Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 9:07 AM
Subject: Re: Category.assert() disappointing
Hello,
Log4j is a logging library. As such, it does not have the mandate to halt the hosting
application. What you are requesting goes
against this basic principle.
The Category.assert() method was added over a year ago. At that time, we went through
a similar discussion and it was agreed to have
Category.assert() log an error message but not abort. During those 12+ months, this is
the first time that I hear a complaint about
the issue. This does not mean you are wrong but derision is definitely unwarranted.
I think it was a mistake to add Category.assert because
1) It does not abort as many people would expect it.
2) log4j is a logging library.
At this stage I am inclined to first deprecate and then remove Category.assert()
unless someone finds it useful and actually uses it
*as is*. For reasons that are not hard to imagine, it is out of question to change the
existing non-abort behavior.
Regards, Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
