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() obvio

Re: Category.assert() disappointing

Category.assert() disappointing >> >> >> 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

Re: Category.assert() disappointing

e the existing Category.assert function as it stand right now, serve no meaningful purpose. > > Cheers > > Simon Liu ZC >> -Original Message- >> From:Zart Colwing [SMTP:[EMAIL PROTECTED]] >> Sent:Thursday, June 21, 2001 10:51 PM >> To:LOG4J

How to add a Renderer to the default hierarchy with the new API

The title say it all... it used to be : Category.getDefaultHierarchy().addRenderer( MyClass.class, new MyClassRenderer()); and now it is Your help will be appreciated. ZC. -- To unsubscribe, e-mail: For additional comm

Adding a Renderer

Please what is the path to add a Renderer with the new 1.2 API ? it used to be : Category.getDefaultHierarchy().addRenderer( MyClass.class, new MyClassRenderer()); But now Category.getDefaultHierarchy() is deprecated -replaced by LogManager.getLoggerRepos