I'm having problems trying to get lazy="no-proxy" to work using
NHibernate 3.0.0. Everything I tried - even the unit tests in the
NHibernate.Test project - result in the property getting eager-loaded
along with its parent object. Or is this the expected behavior?
Here's what I did: in NHibernate.Test/GhostProperty/Order.cs I put a
breakpoint in the Order.Payment property's set accessor. When I run
the GhostPropertyFixture.WillNotLoadGhostPropertyByDefault() method (I
run tests from within Visual Studio), the breakpoint is reached while
the Order object is being loaded ("session.Get<Order>(1)"), from which
I conclude that the Payment property was eagerly loaded... There's
another thing that to me looks strange: after loading, the test method
calls NHibernateUtil.IsPropertyInitialized (to ascertain that the
property wasn't loaded) which gives a false value although the
property is clearly initialized.
Am I missing something, is this a bug somewhere or did I somehow get
my copy of the NHibernate source to act strangely?
Thanks in advance!
--
You received this message because you are subscribed to the Google Groups
"nhusers" 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/nhusers?hl=en.
