Hi,

I have found a problem with accessing a collections in lazy persistent objects from methods marked as internal. The collections are not initialized and they are not either associated with Nhibernate (they do not implement IPersistentCollection interface). For example, I get zero as result of Count proprty on collection that contains many items when it is accessed from internal method.

As required, all my public and protected methods and properties are marked as virtual, and the same is true for my internal methods. As far as I can understand, NHibernate overrides these method and properties.

My question is, if the fact that internal methods are not overrided is feature by design because it simply is not possible or it can be done in some way and I found a bug? :-)

Many thanks for answer.
David

Please,

can someone post me which method of NHibernate I can use from my internal method to give NHibernate know to initialize an object?

Thanks David

Write an public virtual empty method called "ForceInitialization" (or smth)?

Gert

Yes. I did it, but it did not help. I cannot uderstand why :-).

DynamicProxy probably can't override internal methods because .NET doesn't allow it to. You can force initialization of a proxy using NHibernateUtil.Initialize(proxy).

Many thanks, Sergey.

Please can you briefly explain me why it does not help to call empty public virtual method (called "Ping" or "Initialize") on domain object from the internal method to force initialization? Is NHibernate monitoring if the call is done outside of object or it has another reason?

Thanks again.

When a proxy is initialized, a new object of that type is created, so for a proxied class A you actually end up with two objects: the proxy, of class ProxyA (derived from A and overriding its virtual methods), and the real object of class A. This implementation leads to these kinds of interesting side effects.