[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-3229) Make cascade rules more transparent/explicit/deterministic

[Gail Badner (JIRA)]

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

Gail Badner resolved HHH-3229.
------------------------------

    Resolution: Fixed

Committed to trunk / 3.2

> Make cascade rules more transparent/explicit/deterministic
> ----------------------------------------------------------
>
>                 Key: HHH-3229
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3229
>             Project: Hibernate3
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.2.4.sp1, 3.2.5, 3.2.6
>            Reporter: Chris Bredesen
>            Assignee: Gail Badner
>             Fix For: 3.2.x, 3.3.0.CR2
>
>
> Cascade rules are prone to different behavior based on the order in which properties appear in mapping XML.  It is possible that an unexpected TransientObjectException may arise from certain operations when an object graph with circular references is merged (and possibly persisted/updated, etc).
> For example, if a transient instance is reachable through more than once path from a root entity, it is not clear whether operations will be cascaded to it.  The order in which the properties are mapped plays a part in determining cascade paths, but the rules are not documented. 
> Possible resolutions include:
> 1. Documenting the rules so that a programmer can make educated decisions about mapping.
> 2. Enhancing the algorithm such that order no longer matters and the rules are deterministic. 
> 3. ???

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