[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1280?page=all ]
Reto Urfer updated HHH-1280:
----------------------------
Attachment: Fix.zip
I have attached a possible fix to this problem. I did these changes because the problem
blocked our current development. It contains the following changes:
1. Does no longer throw an exception if the entity has not yet been stored in the
database.
2. Removes the already registered insert action from the action queue
Cascade refresh and new instances
---------------------------------
Key: HHH-1280
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1280
Project: Hibernate3
Type: Bug
Components: core
Reporter: Gavin King
Attachments: Fix.zip
I have a report that if you have a managed object, with a reference to a new object,
where cascade refresh is enabled, and you refresh the managed object, then you will get an
exception as refresh tries to cascade to the new object. In fact, the new object should
just be ignored.
Looking at the code, this does appear to be the case.
--
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