Oops, yes, looking at my actual facility config you can see why
logging.config was my filename:
<facility
id="logging"
type="Castle.Facilities.Logging.LoggingFacility,
Castle.Facilities.Logging"
configFile="logging.config"
loggingApi="log4net" />
As for the reference question, I don't *think* you need a reference to
log4net but you will need it in your application directory.
On Wed, May 20, 2009 at 9:52 PM, George Mauer <[email protected]> wrote:
>
> Thanks all, I finally got log4net working!
> Between colin pointing out that I was missing the config and log4net
> nodes and watching the internal debug messages I was able to get it.
> For one thing it seems that the default log config name is
> log4net.config not logging.config - once I made those 2 changes it
> started working.
>
> I do have one more question though. Do I need to have a reference to
> log4net.dll or is the Castle.Facilities.Logging.Log4netIntegration
> sufficient?
>
> On May 20, 3:30 pm, Colin Ramsay <[email protected]> wrote:
> > That config is wrong, you need the configuration and log4net root
> elements.
> > Here's a sample from one of my projects:
> >
> > <?xml version="1.0" encoding="utf-8" ?>
> > <configuration>
> > <log4net>
> > <appender name="SmtpAppender"
> type="log4net.Appender.SmtpAppender">
> > <to value="[email protected]" />
> > <from value="[email protected]" />
> > <subject value="Error" />
> > <smtpHost value="localhost" />
> > <bufferSize value="512" />
> > <lossy value="true" />
> > <evaluator type="log4net.Core.LevelEvaluator">
> > <threshold value="ERROR"/>
> > </evaluator>
> > <layout type="log4net.Layout.PatternLayout">
> > <conversionPattern value="%newline%date [%thread]
> %-5level
> > %logger [%property{NDC}] - %message%newline%newline%newline" />
> > </layout>
> > </appender>
> >
> > <root>
> > <priority value="ALL" />
> > <appender-ref ref="SmtpAppender" />
> > </root>
> >
> > <logger name="NHibernate">
> > <level value="ERROR" />
> > </logger>
> >
> > <logger name="Castle">
> > <level value="ERROR" />
> > </logger>
> >
> > </log4net>
> > </configuration>
> >
> > On Wed, May 20, 2009 at 9:02 PM, George Mauer <[email protected]> wrote:
> >
> > > Ok, so now I have the logging.config file
> > > <?xml version="1.0" encoding="utf-8" ?>
> > > <appender name="RollingFile"
> > > type="log4net.Appender.RollingFileAppender">
> > > <file value="di.log" />
> > > <appendToFile value="true" />
> > > <maximumFileSize value="100KB" />
> > > <maxSizeRollBackups value="2" />
> >
> > > <layout type="log4net.Layout.PatternLayout">
> > > <conversionPattern value="%level %thread %logger - %message
> > > %newline" />
> > > </layout>
> > > </appender>
> >
> > > <root>
> > > <level value="DEBUG" />
> > > <appender-ref ref="RollingFile" />
> > > </root>
> >
> > > The logging.config is set to copy always. No attribute in
> > > AssemblyInfo, and nothing in my App.config.
> > > Still no luck.
> >
> > > On May 20, 2:52 pm, Colin Ramsay <[email protected]> wrote:
> > > > And actually, looking at your links, the coderant one says "3. Add
> the
> > > > log4net config file to the root of the web application:" and the one
> from
> > > > the castle list specifies a config file in the facility configuration
> > > > ("<facility id="loggingfacility"
> > > > configFile="RSS.KM.DataAccess.Tests.dll.config"")... I think if you
> omit
> > > the
> > > > configFile attribute then it just uses logging.config.
> >
> > > > On Wed, May 20, 2009 at 8:49 PM, Colin Ramsay <[email protected]
> >
> > > wrote:
> > > > > I always have the config in logging.config in my application root,
> > > rather
> > > > > than in the app/web.config, I think that's a logging facility
> thing.
> > > You can
> > > > > actually enable log4net internal debugging to find out what's going
> on
> > > in
> > > > > there. Take a look at "How do I enable log4net internal debugging?"
> in
> > > > >http://logging.apache.org/log4net/release/faq.html
> >
> > > > > On Wed, May 20, 2009 at 8:20 PM, George Mauer <[email protected]>
> > > wrote:
> >
> > > > >> I have never used log4net before nor the windsor logging facility,
> I
> > > > >> have gotten the logging facility to work with the console logger
> and
> > > > >> now am trying to set it up with log4net and hitting a roadblock.
> > > > >> Going off the information in this article:
> >
> > > > >>
> http://mikehadlow.blogspot.com/2008/06/more-windsor-love-using-log4ne.
> > > ..
> > > > >> and this earlier post:
> > > > >>
> http://groups.google.com/group/castle-project-users/browse_thread/thr.
> > > ..
> >
> > > > >> I have set up this attribute in my AssemblyInfo.cs file
> > > > >> [assembly: log4net.Config.XmlConfigurator(Watch = true)]
> >
> > > > >> and this is my current App.config :http://pastebin.com/f77d62a4c
> >
> > > > >> Yet nothing appears and I break and inspect my Logger property I
> see
> > > > >> that it is populated with
> > > > >> {log4net.Repository.Hierarchy.DefaultLoggerFactory+LoggerImpl}
> > > > >> Castle.Core.Logging.ILogger
> > > > >> {Castle.Services.Logging.Log4netIntegration.Log4netLogger}
> > > > >> IsDebugEnabled false bool
> > > > >> IsErrorEnabled false bool
> > > > >> IsFatalEnabled false bool
> > > > >> IsFatalErrorEnabled false bool
> > > > >> IsInfoEnabled false bool
> > > > >> IsWarnEnabled false bool
> >
> > > > >> Seems like IsDebugEnabled is not being set. But why?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---
