Hey Nicko,
Nicko Cadell wrote:
Interfaces have been used to allow alternative implementations to be
substituted. At the current time there are no alternative
implementations of ILoggerRepostiroy and ILogger in the log4net source,
however you could supply your own alternative implementation, which
w
Oliver,
> > log4net.Repository.Hierarchy.Hierarchy h =
> >(log4net.Repository.Hierarchy.Hierarchy)log4net.LogManager.Ge
> tLoggerRepository();
> >
> >
> Why do you assume that this ILoggerRepository is really a Hierarchy?
Currently the only implementation of the ILoggerRepository interface is
Hey Nicko,
you may have noticed that you answered my recent question ("Finding out
whether a specific appender is attached") with this, too (although I
haven't tried it yet). Just two comments inline below:
Nicko Cadell wrote:
You can get all the current appenders by using a method like:
public
age-
> From: Dan Johnston [mailto:[EMAIL PROTECTED]
> Sent: 04 December 2004 00:46
> To: log4net-user@logging.apache.org
> Subject: Log4Net API to get appender config properties
>
>
> Is it possible to access appender properties via the log4Net
> API. For instance, I a
PM
To:
log4net-user@logging.apache.org
Subject: Log4Net API to get
appender config properties
Is it possible to access appender properties via
the log4Net API. For instance, I am interested in discovering the name of
a rollingfileAppender logfile name and path, but because it is dynamically
cr
Is it possible to access appender
properties via the log4Net API. For instance, I am interested in
discovering the name of a rollingfileAppender logfile name and path, but
because it is dynamically created with respect to time, parsing the log4net
config file proves futile.
It would appear that
