[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4726) Add support for delete-orphan cascading to <one-to-one/>

[Steve Ebersole (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35263#action_35263 ] 

Steve Ebersole commented on HHH-4726:
-------------------------------------

For components (@Embeddable) there are actually 2 potential (short term) solutions:
1) pull snapshot as mentioned previously
2) have ComponentType track which one-to-one paths were null during hydrate/resolve into the EntityEntry (Cascade could then use that info from EntityEntry to determine which are orphans).  The difficulty here (of course there has to be something right?) is that ComponentType does not know its "path" really.

> Add support for delete-orphan cascading to <one-to-one/>
> --------------------------------------------------------
>
>                 Key: HHH-4726
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4726
>             Project: Hibernate Core
>          Issue Type: New Feature
>          Components: core
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 3.5.0-Beta-4
>
>          Time Spent: 1 day, 5 hours, 31 minutes
>  Remaining Estimate: 0 minutes
>
> JPA 2 requires support for this.  See section "11.1.37 OneToOne Annotation" wrt the orphanRemoval attribute

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