Well, I'd still like to know more about it, but I haven't had any
problems now with leaving out the reference and web.config section. I
guess you only need to add them if you want logging by log4net.
Brian
Brian Kierstead wrote:
Can anyone explain to me why is meant by the new version not having a
dependency on log4net? I'm getting a little confused when reading the
docs and readme files. In the changelog.txt file under the
IBatisNet.DataMapper-bin-1.3.0 directory it says (it has a similar
file in the DataAccess directory which says the same thing):
Added custom logger support (remove dependcy on log4net), IBATIS now
need a custom section in your application config file
Exemple (for log4NET) :
<configSections>
<sectionGroup name="iBATIS">
<section name="logging"
type="IBatisNet.Common.Logging.ConfigurationSectionHandler,
IBatisNet.Common" />
</sectionGroup>
<section name="log4net"
type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" />
</configSections>
<iBATIS>
<logging>
<logFactoryAdapter
type="IBatisNet.Common.Logging.Impl.Log4NetLoggerFA,
IBatisNet.Common.Logging.Log4Net">
<arg key="configType" value="inline" />
</logFactoryAdapter>
</logging>
</iBATIS>
How is this removing the dependancy on log4net? Its still in there...
And in the documentation for the data access, under 'Setup the
Distribution' it says that you need to include log4net (it doesn't say
this in the mapper help file):
The core DataAccess framework has external dependencies on
1. |Castle.DynamicProxy.dll| (creating proxies)
2. |log4net.dll| (logging)
So do we need it or not? Or do you only need to include it in the
web.config if it you want the logging to be used?
Thanks,
Brian
