[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3799) PersistentSet does not honor hashcode/equals contract when loaded eagerly

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3799?page=c... ] Oliver Meyn commented on HHH-3799: ---------------------------------- This is proving painful for us - we typically fetch an object, serialize it, and send it off via JMS. When an object that contains a collection gets deserialized on the other end, it goes boom due to this bug. So we're using the return new HashSet(originalSet) workaround which "solves" the messaging problem. But when work has to happen close to the db and the object (say User has a field called name, and has a collection of Addresses) gets updated (updating only name) Hibernate looks at the collection and sees an entirely new object, so deletes the old collection and writes a new one, even though the data (the Addresses) are all the same. This forces a bunch of unnecessary work in the db. So +1 on upgrading to Major. -- 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