[hibernate-issues] [Hibernate-JIRA] Created: (HHH-4715) Unexpected results when an entity that is already modifiable is set to modifiable again

[Gail Badner (JIRA)]

Unexpected results when an entity that is already modifiable is set to modifiable again
---------------------------------------------------------------------------------------

                 Key: HHH-4715
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4715
             Project: Hibernate Core
          Issue Type: Bug
            Reporter: Gail Badner
            Assignee: Gail Badner


If an entity that is already set to modifiable is updated, then set to modifiable again, the updates will not be flushed on commit.

This is because there is no check to see if the entity is already modifiable before 
changing the snapshot to match the current (updated) entity state in the session. On flush, the current state of the entity in the session is compared with its snapshot. Since it is the same, the entity appears to not be dirty, so the updates are not persisted.

The fix for this is to not change the snapshot when an entity is set to modifiable if that entity is already modifiable.

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