You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-cs@ibatis.apache.org by Bob Hanson <mn...@gmail.com> on 2005/09/27 17:15:48 UTC
log4net 1.2.9
I tried searching for this topic but found no matches.
I recently put my current project into pseudo-production. i.e. It's IN it's
just not being used yet. :)
Then Spring.NET came out with the 1.0 release right after I released. I want
to re-release with the latest version of Spring.NET since it's the official
release. However it is using log4net 1.2.9 and I think I'm experiencing a
build problem between iBatis (SVN 179390) and Spring.
Should/can I re-build SVN179390 with log4net 1.2.9 or should/can I do it
with a different SVN version?
Thanks,
Bob
Re: log4net 1.2.9
Posted by Bob Hanson <mn...@gmail.com>.
That's fine but if the ibatis site isn't going to provide easy links to
regular SVN builds I definitely don't want to keep re-building for my own
production builds. That's not meant as a criticism of the site. It's just
the reality of juggling iBatis builds with your own production builds. I
assume that a linked build is at least considered "stable enough to use".
On 9/27/05, Ron Grabowski <ro...@yahoo.com> wrote:
>
> This issue has been fixed in SVN for the past couple weeks. The only
> external dependency IBatisNet has now is on Castle Dynamic Proxy.
>
> Its possible to use IBatisNet with log4net 1.2.0 beta 8, log4net 1.2.9
> beta, NLog, MS Logging Block, etc.
>
> --- Bob Hanson <mn...@gmail.com> wrote:
>
> > Thanks for the reply. I know it has been discussed before so I was
> > surprised
> > that a search couldn't find anything.
> >
> > I decided to just re-build SVN179390 with log4net 1.2.9
> >
> > This is an annoying issue when you consider a project like Spring
> > that is
> > designed to remove dependencies. Yet you end up with build dependency
> > issues. We had "DLL hell". I wonder what cutsie name this gets.
> >
> > I'm not sure why assemblies should need to dump all of the assemblies
> > they
> > reference into a common bin directory. It would seem to me that some
> > kind of
> > solution could be created so that a referenced assembly goes to the
> > bin
> > directory but its own local references are copied to a sub-directory
> > or some
> > other location.
> >
> > So you'd end up with something like:
> > MyApp/bin/MyApp.exe
> > MyApp/bin/AnAssemblyReference.dll
> > MyApp/bin/AnAssemblyReference/*.dll (assemblies that
> > AnAssemblyReference.dllreference)
> >
> > You could also allow an assembly to be marked as "locally global" (or
> > some
> > such name) which simply shares it in the main bin directory.
> >
> > There probably are some good reasons why it's not that simple but
> > it's
> > easier for me to just speculate rather than investigate. :)
> >
> > On 9/27/05, Chad Humphries <ch...@gmail.com> wrote:
> > >
> > > Bob,
> > >
> > > This was on the list a bit back. I wasn't able to find a link to
> > the
> > > original post so here is the summary.
> > >
> > > This link
> > > http://forum.springframework.net/viewtopic.php?p=827&highlight=#827
> > > lists the web.config entry for a binding redirect. I believe you
> > have
> > > to add a reference to the new log4net to your web project as well.
> > > The new version of ibatis will have a logfactoryadapter to remove
> > > these kind of issues.
> > >
> > > -Chad
> > >
> > > On 9/27/05, Bob Hanson <mn...@gmail.com> wrote:
> > > > I tried searching for this topic but found no matches.
> > > >
> > > > I recently put my current project into pseudo-production. i.e.
> > It's IN
> > > it's just not being used yet. :)
> > > >
> > > > Then Spring.NET came out with the 1.0 release right after I
> > released. I
> > > want to re-release with the latest version of Spring.NET since it's
> > the
> > > official release. However it is using log4net 1.2.9 and I think I'm
> > > experiencing a build problem between iBatis (SVN 179390) and
> > Spring.
> > > >
> > > > Should/can I re-build SVN179390 with log4net 1.2.9 or should/can
> > I do it
> > > with a different SVN version?
> > > >
> > > > Thanks,
> > > > Bob
> > > >
> > >
> >
>
>
RE: log4net 1.2.9
Posted by Ron Grabowski <ro...@yahoo.com>.
A good starting point would be if someone who is knowledgable with the
Logging Block could make a .zip file that shows a basic MS Logging
Block setup. For example if I were doing something for log4net the five
important peices would be:
1)
log4net.dll
2)
log4net.Config.XmlConfigurator.ConfigureAndWatch(
new System.IO.FileInfo(
AppDomain.CurrentDomain.SetupInformation.ApplicationBase +
"log4net.config"));
3)
<log4net>
<appender name="FileAppender" type="log4net.Appender.FileAppender">
<file value="log.txt" />
<layout type="log4net.Layout.SimpleLayout" />
</appender>
<root>
<level value="ALL" />
<appender-ref ref="FileAppender" />
</root>
</log4net>
4)
private readonly static ILog log =
LogManager.GetLogger(
System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);
5)
log.Debug("Hello World");
>From there someone should be able to implement these two interfaces:
http://tinyurl.com/dh4f5
http://svn.apache.org/repos/asf/ibatis/trunk/cs/mapper/IBatisNet.Common/Logging/ILoggerFactoryAdapter.cs
http://tinyurl.com/83dr3
http://svn.apache.org/repos/asf/ibatis/trunk/cs/mapper/IBatisNet.Common/Logging/ILog.cs
--- Peter Mills <de...@peter.mills.to> wrote:
> Being able to use IBatisNet with the MS Logging Block would be
> fantastic for
> my project, due to our use of other MS Application Blocks. Is there
> any
> information available on setting this up?
>
> Cheers,
>
> Peter
>
> -----Original Message-----
> From: Ron Grabowski [mailto:rongrabowski@yahoo.com]
> Sent: Tuesday, September 27, 2005 3:27 PM
> To: user-cs@ibatis.apache.org
> Subject: Re: log4net 1.2.9
>
> This issue has been fixed in SVN for the past couple weeks. The only
> external dependency IBatisNet has now is on Castle Dynamic Proxy.
>
> Its possible to use IBatisNet with log4net 1.2.0 beta 8, log4net
> 1.2.9
> beta, NLog, MS Logging Block, etc.
>
> --- Bob Hanson <mn...@gmail.com> wrote:
>
> > Thanks for the reply. I know it has been discussed before so I was
> > surprised
> > that a search couldn't find anything.
> >
> > I decided to just re-build SVN179390 with log4net 1.2.9
> >
> > This is an annoying issue when you consider a project like Spring
> > that is
> > designed to remove dependencies. Yet you end up with build
> dependency
> > issues. We had "DLL hell". I wonder what cutsie name this gets.
> >
> > I'm not sure why assemblies should need to dump all of the
> assemblies
> > they
> > reference into a common bin directory. It would seem to me that
> some
> > kind of
> > solution could be created so that a referenced assembly goes to the
> > bin
> > directory but its own local references are copied to a
> sub-directory
> > or some
> > other location.
> >
> > So you'd end up with something like:
> > MyApp/bin/MyApp.exe
> > MyApp/bin/AnAssemblyReference.dll
> > MyApp/bin/AnAssemblyReference/*.dll (assemblies that
> > AnAssemblyReference.dllreference)
> >
> > You could also allow an assembly to be marked as "locally global"
> (or
> > some
> > such name) which simply shares it in the main bin directory.
> >
> > There probably are some good reasons why it's not that simple but
> > it's
> > easier for me to just speculate rather than investigate. :)
> >
> > On 9/27/05, Chad Humphries <ch...@gmail.com> wrote:
> > >
> > > Bob,
> > >
> > > This was on the list a bit back. I wasn't able to find a link to
> > the
> > > original post so here is the summary.
> > >
> > > This link
> > >
> http://forum.springframework.net/viewtopic.php?p=827&highlight=#827
> > > lists the web.config entry for a binding redirect. I believe you
> > have
> > > to add a reference to the new log4net to your web project as
> well.
> > > The new version of ibatis will have a logfactoryadapter to remove
> > > these kind of issues.
> > >
> > > -Chad
> > >
> > > On 9/27/05, Bob Hanson <mn...@gmail.com> wrote:
> > > > I tried searching for this topic but found no matches.
> > > >
> > > > I recently put my current project into pseudo-production. i.e.
> > It's IN
> > > it's just not being used yet. :)
> > > >
> > > > Then Spring.NET came out with the 1.0 release right after I
> > released. I
> > > want to re-release with the latest version of Spring.NET since
> it's
> > the
> > > official release. However it is using log4net 1.2.9 and I think
> I'm
> > > experiencing a build problem between iBatis (SVN 179390) and
> > Spring.
> > > >
> > > > Should/can I re-build SVN179390 with log4net 1.2.9 or
> should/can
> > I do it
> > > with a different SVN version?
> > > >
> > > > Thanks,
> > > > Bob
> > > >
> > >
> >
>
>
RE: log4net 1.2.9
Posted by Peter Mills <de...@peter.mills.to>.
Being able to use IBatisNet with the MS Logging Block would be fantastic for
my project, due to our use of other MS Application Blocks. Is there any
information available on setting this up?
Cheers,
Peter
-----Original Message-----
From: Ron Grabowski [mailto:rongrabowski@yahoo.com]
Sent: Tuesday, September 27, 2005 3:27 PM
To: user-cs@ibatis.apache.org
Subject: Re: log4net 1.2.9
This issue has been fixed in SVN for the past couple weeks. The only
external dependency IBatisNet has now is on Castle Dynamic Proxy.
Its possible to use IBatisNet with log4net 1.2.0 beta 8, log4net 1.2.9
beta, NLog, MS Logging Block, etc.
--- Bob Hanson <mn...@gmail.com> wrote:
> Thanks for the reply. I know it has been discussed before so I was
> surprised
> that a search couldn't find anything.
>
> I decided to just re-build SVN179390 with log4net 1.2.9
>
> This is an annoying issue when you consider a project like Spring
> that is
> designed to remove dependencies. Yet you end up with build dependency
> issues. We had "DLL hell". I wonder what cutsie name this gets.
>
> I'm not sure why assemblies should need to dump all of the assemblies
> they
> reference into a common bin directory. It would seem to me that some
> kind of
> solution could be created so that a referenced assembly goes to the
> bin
> directory but its own local references are copied to a sub-directory
> or some
> other location.
>
> So you'd end up with something like:
> MyApp/bin/MyApp.exe
> MyApp/bin/AnAssemblyReference.dll
> MyApp/bin/AnAssemblyReference/*.dll (assemblies that
> AnAssemblyReference.dllreference)
>
> You could also allow an assembly to be marked as "locally global" (or
> some
> such name) which simply shares it in the main bin directory.
>
> There probably are some good reasons why it's not that simple but
> it's
> easier for me to just speculate rather than investigate. :)
>
> On 9/27/05, Chad Humphries <ch...@gmail.com> wrote:
> >
> > Bob,
> >
> > This was on the list a bit back. I wasn't able to find a link to
> the
> > original post so here is the summary.
> >
> > This link
> > http://forum.springframework.net/viewtopic.php?p=827&highlight=#827
> > lists the web.config entry for a binding redirect. I believe you
> have
> > to add a reference to the new log4net to your web project as well.
> > The new version of ibatis will have a logfactoryadapter to remove
> > these kind of issues.
> >
> > -Chad
> >
> > On 9/27/05, Bob Hanson <mn...@gmail.com> wrote:
> > > I tried searching for this topic but found no matches.
> > >
> > > I recently put my current project into pseudo-production. i.e.
> It's IN
> > it's just not being used yet. :)
> > >
> > > Then Spring.NET came out with the 1.0 release right after I
> released. I
> > want to re-release with the latest version of Spring.NET since it's
> the
> > official release. However it is using log4net 1.2.9 and I think I'm
> > experiencing a build problem between iBatis (SVN 179390) and
> Spring.
> > >
> > > Should/can I re-build SVN179390 with log4net 1.2.9 or should/can
> I do it
> > with a different SVN version?
> > >
> > > Thanks,
> > > Bob
> > >
> >
>
Re: log4net 1.2.9
Posted by Ron Grabowski <ro...@yahoo.com>.
This issue has been fixed in SVN for the past couple weeks. The only
external dependency IBatisNet has now is on Castle Dynamic Proxy.
Its possible to use IBatisNet with log4net 1.2.0 beta 8, log4net 1.2.9
beta, NLog, MS Logging Block, etc.
--- Bob Hanson <mn...@gmail.com> wrote:
> Thanks for the reply. I know it has been discussed before so I was
> surprised
> that a search couldn't find anything.
>
> I decided to just re-build SVN179390 with log4net 1.2.9
>
> This is an annoying issue when you consider a project like Spring
> that is
> designed to remove dependencies. Yet you end up with build dependency
> issues. We had "DLL hell". I wonder what cutsie name this gets.
>
> I'm not sure why assemblies should need to dump all of the assemblies
> they
> reference into a common bin directory. It would seem to me that some
> kind of
> solution could be created so that a referenced assembly goes to the
> bin
> directory but its own local references are copied to a sub-directory
> or some
> other location.
>
> So you'd end up with something like:
> MyApp/bin/MyApp.exe
> MyApp/bin/AnAssemblyReference.dll
> MyApp/bin/AnAssemblyReference/*.dll (assemblies that
> AnAssemblyReference.dllreference)
>
> You could also allow an assembly to be marked as "locally global" (or
> some
> such name) which simply shares it in the main bin directory.
>
> There probably are some good reasons why it's not that simple but
> it's
> easier for me to just speculate rather than investigate. :)
>
> On 9/27/05, Chad Humphries <ch...@gmail.com> wrote:
> >
> > Bob,
> >
> > This was on the list a bit back. I wasn't able to find a link to
> the
> > original post so here is the summary.
> >
> > This link
> > http://forum.springframework.net/viewtopic.php?p=827&highlight=#827
> > lists the web.config entry for a binding redirect. I believe you
> have
> > to add a reference to the new log4net to your web project as well.
> > The new version of ibatis will have a logfactoryadapter to remove
> > these kind of issues.
> >
> > -Chad
> >
> > On 9/27/05, Bob Hanson <mn...@gmail.com> wrote:
> > > I tried searching for this topic but found no matches.
> > >
> > > I recently put my current project into pseudo-production. i.e.
> It's IN
> > it's just not being used yet. :)
> > >
> > > Then Spring.NET came out with the 1.0 release right after I
> released. I
> > want to re-release with the latest version of Spring.NET since it's
> the
> > official release. However it is using log4net 1.2.9 and I think I'm
> > experiencing a build problem between iBatis (SVN 179390) and
> Spring.
> > >
> > > Should/can I re-build SVN179390 with log4net 1.2.9 or should/can
> I do it
> > with a different SVN version?
> > >
> > > Thanks,
> > > Bob
> > >
> >
>
Re: log4net 1.2.9
Posted by Bob Hanson <mn...@gmail.com>.
Thanks for the reply. I know it has been discussed before so I was surprised
that a search couldn't find anything.
I decided to just re-build SVN179390 with log4net 1.2.9
This is an annoying issue when you consider a project like Spring that is
designed to remove dependencies. Yet you end up with build dependency
issues. We had "DLL hell". I wonder what cutsie name this gets.
I'm not sure why assemblies should need to dump all of the assemblies they
reference into a common bin directory. It would seem to me that some kind of
solution could be created so that a referenced assembly goes to the bin
directory but its own local references are copied to a sub-directory or some
other location.
So you'd end up with something like:
MyApp/bin/MyApp.exe
MyApp/bin/AnAssemblyReference.dll
MyApp/bin/AnAssemblyReference/*.dll (assemblies that
AnAssemblyReference.dllreference)
You could also allow an assembly to be marked as "locally global" (or some
such name) which simply shares it in the main bin directory.
There probably are some good reasons why it's not that simple but it's
easier for me to just speculate rather than investigate. :)
On 9/27/05, Chad Humphries <ch...@gmail.com> wrote:
>
> Bob,
>
> This was on the list a bit back. I wasn't able to find a link to the
> original post so here is the summary.
>
> This link
> http://forum.springframework.net/viewtopic.php?p=827&highlight=#827
> lists the web.config entry for a binding redirect. I believe you have
> to add a reference to the new log4net to your web project as well.
> The new version of ibatis will have a logfactoryadapter to remove
> these kind of issues.
>
> -Chad
>
> On 9/27/05, Bob Hanson <mn...@gmail.com> wrote:
> > I tried searching for this topic but found no matches.
> >
> > I recently put my current project into pseudo-production. i.e. It's IN
> it's just not being used yet. :)
> >
> > Then Spring.NET came out with the 1.0 release right after I released. I
> want to re-release with the latest version of Spring.NET since it's the
> official release. However it is using log4net 1.2.9 and I think I'm
> experiencing a build problem between iBatis (SVN 179390) and Spring.
> >
> > Should/can I re-build SVN179390 with log4net 1.2.9 or should/can I do it
> with a different SVN version?
> >
> > Thanks,
> > Bob
> >
>
Re: log4net 1.2.9
Posted by Chad Humphries <ch...@gmail.com>.
Bob,
This was on the list a bit back. I wasn't able to find a link to the
original post so here is the summary.
This link http://forum.springframework.net/viewtopic.php?p=827&highlight=#827
lists the web.config entry for a binding redirect. I believe you have
to add a reference to the new log4net to your web project as well.
The new version of ibatis will have a logfactoryadapter to remove
these kind of issues.
-Chad
On 9/27/05, Bob Hanson <mn...@gmail.com> wrote:
> I tried searching for this topic but found no matches.
>
> I recently put my current project into pseudo-production. i.e. It's IN it's just not being used yet. :)
>
> Then Spring.NET came out with the 1.0 release right after I released. I want to re-release with the latest version of Spring.NET since it's the official release. However it is using log4net 1.2.9 and I think I'm experiencing a build problem between iBatis (SVN 179390) and Spring.
>
> Should/can I re-build SVN179390 with log4net 1.2.9 or should/can I do it with a different SVN version?
>
> Thanks,
> Bob
>