When, and if, we will don't use log4net will be because NH don't have hard dependency in nothing more than .NET FW. BTW I don't understand which is the problem, or where NLog is better than log4net, or why a NH-user may have so many problems because NH are using log4net...
I can understand that the purpose of Common.Logging if abstraction from logging system but, really, how some other dependency make NH purposes better... Perhaps Common.Logging it is interesting from the point of view of one application but for a FW as NH... 2008/10/26 Brian Chavez <[EMAIL PROTECTED]> > > What I've been talking about is exchanging the dependency on log4net with > Common.Logging. Why? Because this gives the freedom for NHUsers to > choose/plug their logging framework into NHibernate whether it be NLog, > log4net, or EntLib Logging. > > If NHUsers don't want (or use) any of the logging frameworks mentioned, > they > can implement their own ILoggerFractoryAdapter that will work just the > same. > This is the fundamental purpose of Common.Logging. > > http://netcommon.sourceforge.net/doc-latest/reference/html/logging.html > > I guess if you want to break the dependency on log4net AND keep > Common.Logging out all together, then NH needs its own Logging that is > pluggable. > Possibly, a NHibernate.Logging namespace with some interfaces that NHUsers > can implement, and a LoggerFactory type that can be defined in an NH Config > File. However, I think this approach is basically reinventing the wheel > because Common.Logging already has this functionality. > > -Brian > > > ---------------------------------------------- > Brian Chavez > Bit Armory, Inc. > http://www.bitarmory.com > > > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of josh robb > Sent: Sunday, October 26, 2008 4:37 AM > To: [email protected] > Subject: [nhibernate-development] Re: NH Logging Abstraction > > > On Sun, Oct 26, 2008 at 9:59 PM, Fabio Maulo <[EMAIL PROTECTED]> wrote: > > Wait a minute... > > If we will remove the dependency from log4net is because we don't want > any > > other dependency. > > I mean.... if we will remove dependency from log4net is not to have a > > dependency to Common.Logging. > > Clear, no? > > Exactly - there are two separate ideas here: > > 1. NH-Devs - Removing static third party dependancies. > 2. Brian - Allowing using other logging frameworks. > > Replacing a hard dependancy on log4net with one on Common.Logging > isn't really a huge win for 1 - but it might be for 2. > > j. > > -- Fabio Maulo
