> I have a custom appender that uses parameters from the App.config file,
> however
> I need to call an internal method after instantiation once the fields have
> been populated.
>
> I see PreAppendCheck however I only need this done once. Does such a facility
> exist?
Sorry for the noise folk
Trying that again...
I have a custom appender that uses parameters from the App.config file, however
I need to call an internal method after instantiation once the fields have been
populated.
I see PreAppendCheck however I only need this done once. Does such a facility
exist?
Thanks!
jlc
If you extend a class, then that classes definition is part of your
definition, and thus the extended class must be available to anyone using
your class in order to compile.
If you completely wrap a class and translate all calls to and from it, then
it would not be needed by anyone referencing you
> To: log4net-user@logging.apache.org
> Subject: Re: Custom Appender
>
> Thanks for that - I was thinking along the lines of pass my
> XML in as the message. The only problem with that was the
> fact that it didn't seem to fit in with the config
> 'philosop
f the sample ADO appender.
>
>Blimey, sorry to go on and on!
>
>Yes, any example code would be great - please pass it on, and many thanks
>for your email
>
>Regards
>
>Ian
>
>
>
>
>
>
>-Original Message-
>From: Simon Wallis [mailto:[EMAIL
OTECTED]
Sent: 22 November 2004 18:26
To: log4net-user@logging.apache.org; [EMAIL PROTECTED]
Subject: Re: Custom Appender
Hi Ian,
No, you don't need to do anything to the LoggingEvent class. You create your
own appender and override the Append(LoggingEvent loggingEvent) method. In
this function you
PROTECTED]
Sent: 22 November 2004 18:26
To: log4net-user@logging.apache.org; [EMAIL PROTECTED]
Subject: Re: Custom Appender
Hi Ian,
No, you don't need to do anything to the LoggingEvent class. You create your
own appender and override the Append(LoggingEvent loggingE
Hi Ian,
No, you don't need to do anything to the LoggingEvent class. You create your
own appender and override the Append(LoggingEvent loggingEvent) method. In this
function you can access loggingEvent.MessageObject, which will give you the
message you logged from your code -- in your case, an
