[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1565?page=comments#action_22468 ]
Daniel Stern commented on HHH-1565:
-----------------------------------
I checked this issue also in the actual developer version 3.2 of Hibernate. It didn't work yet. When I add a new child record to a parent and invoke the refresh action, the transient ( new ) objects produces an UnresolvableObjectException. I think, this Exception could be
omitted, because the refresh of the parent automatically removes the this "new" child.
A further problem is, that the "unsaved-value" parameter in the <id> tag of the hibernate mapping file takes no effect, if the new object has a "null" id.
e.g. <id name="aPK" type="java.lang.Long" column="ADDRESS_PK" unsaved-value="null" >
In this case the refresh process breaks with a AssertionFaiure "null id". This should be checked and identified as a new transient object ( no refresh necessary ).
see: org.hibernate.event.def.DefaultRefreshEventListener.onRefresh
> Cascade refresh and new instances
> ----------------------------------
>
> Key: HHH-1565
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1565
> Project: Hibernate3
> Type: Bug
> Components: core
> Reporter: Daniel Stern
>
>
> 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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
