Here is what the javadoc says about Category.assert():
"If assertion parameter is false, then logs msg as an error statement."
So I guess I would not have expected it to halt ny application.
> -----Original Message-----
> From: Zart Colwing [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 21, 2001 8:16 AM
> To: LOG4J Users Mailing List
> Subject: Category.assert() disappointing
>
>
> I'm disappointed by the Category.assert() function.
>
> It was my belief that when an assert breaks that means that
> the conditions
> for the safe continuation of the program execution are not
> meet and it is
> better to halt the program right away before running into big
> troubles.
>
> Category.assert() obviously doesn't live by the same
> interpretation because
> it never tries to halt the faulty program in any way, shape or form.
> For me Category.assert() is just a way to log at ERROR level,
> not even at
> FATAL level as one could at least expect !
>
> I'm just asking if it is intentional and if yes why so ?
>
>
> Tanks
> ZC
>
>
> ---------------------------------------------------------------------
> 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]
