Fwd: iBatis.NET, Spring.NET - Log4NET DLL Woes

[Rick Evans <un...@gmail.com>]

Hiya

Have you tried a binding redirect in your configuration file... the
same issue arises with regard to NHibernate, and is answered in this
forum posting.

http://forum.springframework.net/viewtopic.php?p=827&highlight=#827

On a related issue, there is no particularly compelling reason for
Spring.NET using the version of Log4Net that it does. This issue has
come up a few times on the Spring.NET mailing list, and on the forum,
so in the interests of just keeping everything simple (it is only
logging), I daresay we (Spring.NET) could synch up our versions of
Log4Net with both iBatis.NET and NHibernate (or vice versa).

I'll ping the rest of the Spring.NET team (actually, I'll just forward
this to our list).

Ciao
Rick

> ---------- Forwarded message ----------
> From: Hai Hoang <ha...@yahoo.com>
> To: user-cs@ibatis.apache.org
> Date: Wed, 31 Aug 2005 09:41:51 -0700 (PDT)
> Subject: ibatis used dated log4net dll
> Apc.Test.Persistence.ApplicationDaoTest.TestGetAllApplications
> : System.TypeInitializationException : The type
> initializer for
> "IBatisNet.DataAccess.Configuration.DomDaoManagerBuilder"
> threw an exception.
>   ----> System.IO.FileLoadException : The located
> assembly's manifest definition with name 'log4net'
> does not match the assembly reference.
>
> I am using ibatis.net with spring.net and both project
> uses different version of log4net.  do you know who to
> fix this without download the source code and compile
> it?

Re: Support for mapping of public fields.

[Gilles Bayon <ib...@gmail.com>]

It's not planned in the near futur.
And as this addition is subject to discussion (not best practice), it's not 
sure we support it.
 -Gilles 
 On 9/8/05, Ling Wang <li...@yahoo.com> wrote: 
> 
> Ted,
> 
> I like your book (struts in action). Glad to see you
> active in iBATIS for .Net. I recently posted a message
> saying it would be nice if iBATIS can support mapping
> of public fields besides properties (getters and
> setters). Do you know if that is already on the to do
> list? If yes, any idea when will it be implemented?
> 
> Thanks.
> 
> Ling
> 
>

Re: Support for mapping of public fields.

[Ted Husted <te...@gmail.com>]

As a rule, the best way to get a feature implemented in an open source
project is to try writing the patch yourself. Others can then try the
patch before deciding.

When I first started using iBATIS.Net, I tried populating public
fields myself. Given the way properties are implemented in C#, it does
seem like a likely feature, since you can switch from a  field to a
property without making other changes in your code. If a line reads

Something = "Test";

Something could be a field or it could be a property. The caller
neither knows nor cares, and the definer can change Something from one
form to other without breaking the API.

Of course, sight unseen, there's no guarantee that the patch would be
applied to the main distribution, but it would be there for yourself
and others to use.

-- HTH, Ted.
http://www.husted.com/poe/

On 9/8/05, Ling Wang <li...@yahoo.com> wrote:
> Ted,
> 
> I like your book (struts in action). Glad to see you
> active in iBATIS for .Net. I recently posted a message
> saying it would be nice if iBATIS can support mapping
> of public fields besides properties (getters and
> setters). Do you know if that is already on the to do
> list? If yes, any idea when will it be implemented?
> 
> Thanks.
> 
> Ling

Re: iBatis.NET, Spring.NET - Log4NET DLL Woes

[Gilles Bayon <ib...@gmail.com>]

I think, you could.
CastleDP X.X has no dependency and has never had dependency to log4net.
 -Gilles

 On 9/9/05, Ted Husted <te...@gmail.com> wrote: 
> 
> Gilles,
> 
> Do you think I should also try running with a binding redirect from
> CastleDP 1.1 to CastleDP 1.5 with iBATIS.NET <http://iBATIS.NET> 1.2.1?
> 
> Perhaps we could bring out 1.2.2/1.6.2 point releases that only
> updated the dependencies.
> 
> Does CastleDP 1.5 use log4net anymore? I don't see it in the lastest
> distribution.
> 
> -T.
> 
> On 9/8/05, Ted Husted <te...@gmail.com> wrote:
> > To get the binding redirect to work for me, I had to include a hard
> > reference to log4net version 1.2.0.9 <http://1.2.0.9> in the project, 
> that I didn't
> > have before. But, once I did that, it fell into place.
> >
> > So, now I get to playtest iBATIS.Net against log4net 1.2.0.9<http://1.2.0.9>, 
> without
> > recompiling. :)
> >
> > -T.
>

Re: iBatis.NET, Spring.NET - Log4NET DLL Woes

[Ted Husted <te...@gmail.com>]

Gilles, 

Do you think I should also try running with a binding redirect from
CastleDP 1.1 to CastleDP 1.5 with iBATIS.NET 1.2.1?

Perhaps we could bring out 1.2.2/1.6.2 point releases that only
updated the dependencies.

Does CastleDP 1.5 use log4net anymore? I don't see it in the lastest
distribution.

-T.

On 9/8/05, Ted Husted <te...@gmail.com> wrote:
> To get the binding redirect to work for me, I had to include a hard
> reference to log4net version 1.2.0.9 in the project, that I didn't
> have before. But, once I did that, it fell into place.
> 
> So, now I get to playtest iBATIS.Net against log4net 1.2.0.9, without
> recompiling. :)
> 
> -T.

Support for mapping of public fields.

[Ling Wang <li...@yahoo.com>]

Ted,

I like your book (struts in action). Glad to see you
active in iBATIS for .Net. I recently posted a message
saying it would be nice if iBATIS can support mapping
of public fields besides properties (getters and
setters). Do you know if that is already on the to do
list? If yes, any idea when will it be implemented?

Thanks.

Ling

Re: iBatis.NET, Spring.NET - Log4NET DLL Woes

[Ted Husted <te...@gmail.com>]

To get the binding redirect to work for me, I had to include a hard
reference to log4net version 1.2.0.9 in the project, that I didn't
have before. But, once I did that, it fell into place.

So, now I get to playtest iBATIS.Net against log4net 1.2.0.9, without
recompiling. :)

-T.

On 8/31/05, Rick Evans <un...@gmail.com> wrote:
> Hiya
> 
> Have you tried a binding redirect in your configuration file... the
> same issue arises with regard to NHibernate, and is answered in this
> forum posting.
> 
> http://forum.springframework.net/viewtopic.php?p=827&highlight=#827