When using saveOrUpdate oin one of my entity classes that implement Lifecycle, Lifecycle.onUpdate or Lifecycle.onSave are not called at all. Is this how it is suppose to work or is this a bug? I am using Hibernate 2.0.3.

Thanks

read the javadoc

Gavin,

Thanks for responding. I actually have read the Javadoc and was expecting the when session.saveOrUpdate is called that either save or update will be called on the passed entity. But this is not what I am seeing in my application. This is working when I just use save or update though.

Thanks,

Haytham

And I quote:

Oh, perhaps I have misunderstood your misunderstanding.

You probably think that you can call saveOrUpdate() on an entity that is already associated with the session.

Well, you can, but it is a no-op. Hibernate does automatic dirty checking.

onUpdate() is called when a detached instance is passed to update().

I think I understood what is going on. Here is what I am doing:

I am loading an entity (lets call it EntityA) and adding to one of its collections (called myBs) another entity type (EntityB) then calling saveOrUpdate on it EntityA. This is not resulting in a call to onSave or onUpdate on the parent entity. If I update an entity's collection, will this kind of update be detected by Hibernate as dirty?

My configuration is as follows:

<set name="myBs" lazy="true" table="table_linking_a_to_b">
<key column="a_id"/> <!-- id of entity_A -->
<many-to-many class="my.package.EntityB" column="b_id"/>
</set>

Both entities (A & B) are loaded first then associated by adding an EntityB to EntityA's myBs collection.

Here is a snippet of my code:

//load a
EntityA a = (EntityA )session.load(EntityA .class, a_Id);

//load b, could do this multiple times
EntityB b = (EntityB)session.load(EntityB.class, b_id);

a .getMyBs().add(b);

//I called either one of the following and neither resulted in
//a call to onSave or onUpdate
session.saveOrUpdate(a);
session.update(a);


session.flush();

What could be changed to make this work? It seems just updating EntityA's collection is not enough to trigger an onUpdate call on EntityA.

Thanks.

as Gavin said, Since you loaded A and B from the session, they are already associated to the session. You can remove sessionsaveOrUpdate(a) or session.update(a) : it's useless. Hibernate knows about dirtyness of a (and b) and won't call LifeCycle onUpdate.

epbernard,

I am updating EntityA by the following:

a .getMyBs().add(b);

My question was, does this make EntityA dirty? Seems like it does not.

I also posed the question for an alternative to get what I am trying to do.

If anyone dealth with ths same issue and has a solution to share, I would appreciate a second point of view.

Not an expert on that but an interceptor might help (with the onDirty stuffs).

Thanks. I have started looking at interceptor and the onFlushDirty method.

back to Hibernating...