EntityNotFoundException when performing EntityManager.refres

[waynebagguley]

Here is my scenario. I have an entity bean 'Request' that has a list of entity beans 'Detail'. I use the @OneToMany(cascade=ALL) annotation for the relationship.

I have a page where I can edit 'Request' and add 'Detail' objects to it. If I click 'save' then everything is saved perfectly. If I hit 'discard' then I try and call:

entityManager.refresh(request);

so that the details are reverted back to the database. If I don't add any 'Detail' objects, it works, but if I do add them and then click 'discard' I get this exception:

javax.persistence.EntityNotFoundException: No row with the given identifier exists

I am using

@Begin(flushMode=FlushModeType.MANUAL)

on the initial method and

@End

on the discard method.

I guess that this is because the newly created Detail objects don't exist in the database, but I thought that calling the refresh method would take this possibility into account?

[cptnkirk]

This is really a Hibernate/JPA question, you might get more help from that forum. What I'd expect is happening is that due to your cascade level, refresh is attempting to refresh the database state of your detail entities. Since they don't exist, you get an error.

Perhaps you should enumerate the cascade options you want, and leave out refresh on your detail association.

[fhh]

Or clear the details collection before refreshing if you DO want to cascade on refresh.

Regards

Felix