Hi

When i saves a object the first time I need to update a property and i thought the IInterceptor.OnSave would help me with this but..

In the onSave method I have.



the value is updated and i return true, but it seems like NHibernate doesnt care that I have modified the state of the object, because it tries to insert null. The GetNextValue just return a new guid as a string, so there is nothing strange there. I have even tried to modify the state, by using the propertyNames array but no sucess ther either..

Try the ILifeCycle interface instead. I've never used interceptors, but have had great success with ILifeCycle.

ILifeCycle is an interface that the BLL.Supplier class should implement. It gives you an opportunity to modify the state of a persistent object at key points (load, save, update, etc), and allow you to silently veto operations like save or update.

There is a brief article here on the interface. It explains it well.


Also, make sure that in your mapping file, the SupplierId is mapped with a generator of "assigned", with an appropriate unsaved-value (for guids, this should be "00000000-0000-0000-0000-000000000000").

Hi

Thanks for your reply tylord.

I havent time to test ILifecycle today but it looks like what Im looking for. Read about the ILifeCycle interface for Hibernate and the docs says that onUpdate isnt called when you do a flush. You must pass the object to update method to trigger the onUpdate, do you know if its the same in NHibernate?

And the onSave method. Is that only called when i saves the object for the first time?

Thx again tylord!

It does appear that ILifeCycle in NHibernate behaves the same as Hibernate in that it only triggers OnUpdate on an explicit call to session.Update(). I wasn't aware of this - but some quick tests do show that. I suppose I've dodged this issue in the past since my OnUpdate methods generally didn't contain much.

OnSave will fire only when the object is inserted.

Hi again

Thx for your help tylord! :thumbup

As I currently need to modify the object during the first save ILifeCycle will work perfect for me. But what is a bit annoying is that I dont understand the meaning of the IInterceptors and how to work with them.

Are there somebody who help me understand when and how to use the Interceptors?

In my interceptor, I change the state[] array, not the object.

Here's my code for setting String.Empty to null (a hack for working with Oracle).



2) Is there a reason you're comparing types instead of using the "is" operator?[/code]

Hi

Sorry for the late answer, rponton. (the first week after vacation can be a nightmare).

The short answer is no. Tbh, I dont know if there is any difference.. Is there?