[hibernate-issues] [Hibernate-JIRA] Commented: (HV-281) validation of a persisted map

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-281?page=com... ] Vladimir Klyushnikov commented on HV-281: ----------------------------------------- Hi, I was struggling with this issue all past day. Bad news that this is behaviour by design and it is used to merge entities with collections of other entities that use assigned identifiers (IMHO). But it leads to really annoying problems. First is the issue that is mentioned in description and the second is that merging transient entity with collection executes INSERT and subsequent UPDATE of same entity. I use auditing of my entity and don't need this update. Good news that I've found a simple workaround. It will work only with generated IDs and it is ok for me. I've developed a custom merge listener and registered it: {code} public class CollectionHandlingMergeEventListener extends DefaultMergeEventListener { @Override protected void copyValues(EntityPersister persister, Object entity, Object target, SessionImplementor source, Map copyCache, ForeignKeyDirection foreignKeyDirection) { if (foreignKeyDirection != ForeignKeyDirection.FOREIGN_KEY_TO_PARENT) { Object[] copiedValues = TypeFactory.replace( persister.getPropertyValues(entity, source.getEntityMode()), persister.getPropertyValues(target, source.getEntityMode()), persister.getPropertyTypes(), source, target, copyCache ); persister.setPropertyValues(target, copiedValues, source.getEntityMode()); } } } {code} Of course, it is a hack. Hope core contributors will find a better way to solve these issues. -- 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