If you want to work with filters you must use log4j.xml configuration instead
of log4j.properties. The properties configuration style does not support filter
entries. It's anyway recommended to use xml configuration since:
- the auto configuration mechanisme of log4j looks first for the log4j.xml file
- the properties configuration style is no more supported in future releases
- In my opinion the xml is clearer and more self-documenting than properties
TraceDenyFilter and XMLDenyFilter are self made classes derived from the
log4j....Filter class (see previous mail). They serve only as example how you
can configure your own filter. Note that you can also configure own member
properties of your own filter if they have standard setter methods:
public void setMyProperty( String aValue)
will be configured as
<param name="MyProperty" value="HelloWorld"/>)
The storage location of your self made filter is like any other class:
somewhere in the known classpath.
Heri
> -----Original Message-----
> From: garima015 [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 30, 2006 3:37 PM
> To: [email protected]
> Subject: Re: Log4J System alerts
>
>
>
> Thanks Heri for ur help..
> one thing more i want to ask is is this configuration will be done in
> Log4j.properties..if not then where i have to write all this.And is
> TraceDenyFilter and XMLDenyFilter are self made filters or do
> i have two
> build two classes extending these filters. In case so where i
> have to save
> these filter classes.
>
> ur help is really useful to me
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
