Comments on: Virtual member call in constructor and NHibernate

By: Tigraine

Tigraine — Fri, 07 Nov 2008 23:05:46 +0000

public virtual ISet OrderItems
{
get { return orderItems_; }
set { orderItems_ = value; }
}

private ISet orderItems_;

public Order()
{
orderItems_ = new HashedSet();
}

I know it should work that way, but it doesn't.
Can't say why. But it doesn't work.

Maybe I should have added that the problem is occuring during my Repository unit tests. If I run the tests one by one it works, but if they get executed all together I get the exception.

I think I'll dedicate some more time to the problem tomorrow. But debugging concurrency issues sucks.

By: Ayende Rahien

Ayende Rahien — Fri, 07 Nov 2008 22:55:37 +0000

You set the field in the ctor, not touching the property, and that will work

By: Tigraine

Tigraine — Fri, 07 Nov 2008 20:28:27 +0000

That didn't work.. I tried having a private field that gets accessed through the property and that gets set by the ctor..
I also tried to set the field on demand from the property, but both times I got the “Illegal attempt to associate a collection with two open sessions”.

Thanks anyway, I guess initializing the collection isn't all that difficult after all

By: Ayende Rahien

Ayende Rahien — Fri, 07 Nov 2008 19:33:56 +0000

The solution to this is init the collection via the property, but to initialize the field.