I have implemented an IInterceptor in our repository, because have some processing that needs to take place after an object is loaded. If a transaction is not involved, OnLoad is called, however, NHibernate has not yet populated the object. I was not expecting this behavior, since everything I've read about IInterceptor indicates that OnLoad is called after NHibernate has already loaded the object.

Now, if I use a transaction, after the transaction is complete, I have a fully populated object, but we don't always use transactions.

Am I flat out misunderstanding how this works, or is there another reason why OnLoad is being called, when the object has not actually been loaded by NHibernate?

If you need any more details, let me know, but hopefully I've explained the problem well enough.

Thank you,

D.

That's the way it works. I don't like it either. If you use NH 2.0, you better go with the new event system. If you stick with 1.2 you can implement ILifecycle on your objects. ILifecycle.OnLoad is called after the object is hydrated.

Thank you for your reply.

I will look into moving to 2.0 today, because the changes I'm attempting to implement are vital to the success of our product. So a workable solution must be found.

Thank you again,
D.