[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5784) Save can fail when there is a transient entity reachable by multiple paths and at least one path does not cascade on save

[Strong Liu (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39333#action_39333 ] 

Strong Liu commented on HHH-5784:
---------------------------------

Gail,

would you like take this one?

> Save can fail when there is a transient entity reachable by multiple paths and at least one path does not cascade on save
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-5784
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5784
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>            Reporter: Strong Liu
>
> This issue is the same as JBPAPP-915, but is for the save event. It may also affect persist and save-update events. 
> The fix should be very similar to what was done for JBPAPP-915 and one fix may work for all of these types of events. 
> This issue needs to be fixed to support JDK 1.6. Because the iteration order for HashSets and HashMaps is different for JDK 1.6, cascading operations to entities in a set may be saved in a different order, causing a cascade that worked in a previous version to fail with a TransientObjectException. 
> See HHH-3229 for details. 
> In addition, a note should go into the release notes that the change in order of cascades is a known issue.
> https://issues.jboss.org/browse/JBPAPP-2278

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira