[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5166?page=c... ] Gail Badner resolved HHH-5166. ------------------------------ Assignee: Gail Badner Resolution: Rejected This is expected behavior. When the User was merged with the new Role, the insert and/or update operations were queued, but not flushed. Later, when the transaction was committed, Hibernate tried to flush the insert or update, but the entities were no longer in the session, resulting in AssertionFailure. Calling Session.flush() before evicting the entities will fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5166?page=c... ] Alexandre FRADIN edited comment on HHH-5166 at 4/27/10 3:40 PM: ---------------------------------------------------------------- In fact, I don't want to persist these changes. In my application, I set flushMode to Manual before merging in order to do not flush. I need to merge my entity to access lazy collections and perform validations. I expected that evicting the entity before the flush would cancel insert and update operations. Update operations are cancelled, but not the insert ones, it's a bit strange... If we can't merge and evict an object without flushing updates, update should cause this exception as well (in my opinion). Is it a way to do that (merge and evict without flushing)? Thanks. was (Author: keeg): In fact, I don't want to persist these changes. In my application, I set flushMode to Manual before merging in order to do not flush. I need to merge my entity to access lazy collections and perform validations. I expected that that evicting the entity before the flush would cancel insert and update operations. Update operations are cancelled, but not the insert ones, it's a bit strange... If we can't merge and evict an object without flushing updates, update should cause this exception as well (in my opinion). Is it a way to do that (merge and evict without flushing)? Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5166?page=c... ] Alexandre FRADIN commented on HHH-5166: --------------------------------------- Once again, sorry for my English. I was not looking for help, but trying to explain why this is a bug... I tried to keep my first unit test as simple as possible. May be it was too simple to illustrate the problem. Here a new unit test to show the difference between insert and update operations. In the method testEvictHibernateWithUpdateOnly() : - a user is merged - update operations are queued - a user is evicted - update operations are removed from queue - commit works fine In the method testEvictHibernateWithInsertUpdate(): - a user is merged - insert and update operations are queued - a user is evicted - insert operations are not remove from queue - update operations are removed from queue - commit fails If I follow your logic, both tests should fail and not just the second one : "Later, when the transaction was committed, Hibernate tried to flush the insert or update, but the entities were no longer in the session, resulting in AssertionFailure." It is true for insert, not for update. If evict() method remove update operations from queue, insert should be removed to. I will figure out a way to deal with the behavior, but I think this is a severe fonctional limitation for merge/evcit operations use with cascade="all' entities. Where a simple evict should be cascade to the entity's associations and keep the session clean, I will probably need to implement rollback mecanism and may be split some business methods. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira