logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicko Cadell" <ni...@neoworks.com>
Subject RE: Bug in log4net\extensions\net\1.0\log4net.Ext.EventID??
Date Mon, 17 Jan 2005 17:05:31 GMT
Yes this is a bug in the EventID extension code. The levels passed to
the LoggingEvent constructor should match up with the level in the
method name.
This has been fixed in CVS.

Nicko

> -----Original Message-----
> From: Burger, Erik [mailto:Erik.Burger@Gpxs.net] 
> Sent: 14 January 2005 11:55
> To: Log4NET User
> Subject: Bug in log4net\extensions\net\1.0\log4net.Ext.EventID??
> 
> There seems to be a bug in the EventID extension for log4net. 
> In the interface implementation, all functions have their 
> level set to Level.INFO, as follows:
> 
> public void Warn(int eventId, object message, System.Exception t) {
>   if (this.IsWarnEnabled)
>   { 
>     LoggingEvent loggingEvent = new LoggingEvent((FullName, 
> Logger.Repository, Logger.Name, Level.INFO, message, t); 
>     loggingEvent.Properties["EventID"] = eventId; 
>     Logger.Log(loggingEvent);
>   }
> } 
> 
> Shouldn't this be Level.WARN? The same goes for all the other 
> interface implementations. 
> 
> -------------------------------
> Software Engineer
> Research and Development Group
> GPXS Wireless Ltd. 
> Southampton, United Kingdom
> Phone: +44 (0) 23 8076 2519 
> Fax:     +44 (0) 23 8076 2555 
> Email: erik.burger@gpxs.net 
> 
> 
> The information transmitted by this e-mail message is 
> intended solely for the use of the person to whom or entity 
> to which it is addressed. The message may contain information 
> that is privileged and confidential.  Disclosure, 
> dissemination, distribution, review, retransmission to, other 
> use of or taking any action in reliance upon this information 
> by anyone other than the intended recipient is prohibited. If 
> you are not the intended recipient, please do not 
> disseminate, distribute or copy this communication, by e-mail 
> or otherwise. Instead, please notify us immediately by return 
> e-mail (including the original message with your reply) and 
> then delete and discard all copies of the message.
> 
> Although we have taken precautions to minimize the risk of 
> transmitting viruses we nevertheless advise you to carry out 
> your own virus checks on any attachment to this message. We 
> accept no liability for any loss or damage caused by viruses.
> 
> 

Mime
View raw message