is just a convention and not a must.
Or - of course - both.
Heri
-Ursprüngliche Nachricht-
Von: Angeli106 [mailto:angeli...@gmail.com]
Gesendet: Donnerstag, 18. März 2010 15:51
An: log4j-user@logging.apache.org
Betreff: Re: AW: Path exclusion for logs
Turns out u were right, the pa
Turns out u were right, the parent class(AbstractHttpClient) instantiates the
log like this:
private final Log log = LogFactory.getLog(getClass());
Also turns out that this is a commons.logging logger and not a log4j as i
thought
Also it looks like it's private so i can't override it, any ideas?
Probably the parent class does not instantiate his logger statically but like
this:
Logger logger = Logger.getLogger( this.getClass().getName() );
and therefore it retrieves a logger with the name of your descendant (name
starting with your namespace). If it would instantiate it statically:
st
