[hibernate-issues] [Hibernate-JIRA] Reopened: (HHH-4948) Session.flush() does not always cascade save or update to read-only or immutable entities

[Gail Badner (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gail Badner reopened HHH-4948:
------------------------------


Re-opening because DefaultSaveOrUpdateEventListener.performUpdate() simply reassociates immutable entities. This adds the immutable entity and its collections to the session, but it does not add the entities in the collections to the session. These entities need to be added to the session in order for flush to cascade save-update to these immutable entities.

> Session.flush()  does not always cascade save or update to read-only or immutable entities
> ------------------------------------------------------------------------------------------
>
>                 Key: HHH-4948
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4948
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>            Reporter: Gail Badner
>            Assignee: Gail Badner
>             Fix For: 3.5.0-CR-2
>
>
> When the session contains only read-only or immutable entities, Session.flush() does not cascade save or update operations to these entities unless the session contains at least one entity that is mutable and not read-only.
> Flush should cascade the save-update operation as mapped, but save-update operations should not affect read-only or immutable entities themselves.

-- 
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