A good example will be found here:
http://jaikiran.wordpress.com/2006/07/12/create-your-own-logging-level-in-log4j/
Curt Arnold <[EMAIL PROTECTED]> wrote:
On Dec 6, 2007, at 5:19 PM, chiran wrote:
>
> Hi all,
> It is very easy to create a custom log4j level.
> All u need is the basic understandi
On Dec 6, 2007, at 5:19 PM, chiran wrote:
Hi all,
It is very easy to create a custom log4j level.
All u need is the basic understanding of how the different levels are
organized.
Good example of extending levels for the right reason.
Praveen Kumar Hasthalapuram wrote:
Hi All,
I nee
Hi all,
It is very easy to create a custom log4j level.
All u need is the basic understanding of how the different levels are
organized.
here is the sample code for that.
create a custom level of your own.
package com.custom.log;
import org.apache.log4j.Level;
// Referenced classes of packag
Thanks Philip,
I will go with first solution, because with second soultion may lead
performance overhead and it is time consuming process.
Regards,
Praveen
On 12/29/05, Philip Denno <[EMAIL PROTECTED]> wrote:
>
> I think you misunderstand the idea of level. Levels in log4j are things
> like "DEB
I think you misunderstand the idea of level. Levels in log4j are things
like "DEBUG", "INFO", "WARN", "ERROR", "FATAL". So if your level is set
to INFO and in your call you execute logger.debug(message) - then the
message will be thrown away, because DEBUG < INFO. On the other hand if
you execute l
