[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4601?page=c... ] Scott Marlow reassigned HHH-4601: --------------------------------- Assignee: Scott Marlow -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4601?page=c... ] Steve Ebersole commented on HHH-4601: ------------------------------------- Unlike HHH-4725, this one is pretty trivial since core already supports it -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4601?page=c... ] Edmondo Porcu commented on HHH-4601: ------------------------------------ Why this has been closed?? I have a real problem with OneToMany. If I delete an object like the following public abstract class BondImpl extends SecurityImpl implements BondInterface { @OneToOne(fetch = FetchType.EAGER,mappedBy = "bond",orphanRemoval = true,cascade = CascadeType.ALL) @Cascade(org.hibernate.annotations.CascadeType.ALL) protected BondCouponsCollection bondCouponsCollection; } and then I persist a new one with the same name but a different bondCouponsCollection, the join table between the two is not cleaned upon delete. As a result, when I restart my application and I try to load again the object, it fails with: no single row for entry... Am I missing something? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4601?page=c... ] Edmondo Porcu commented on HHH-4601: ------------------------------------ Yes I am sorry. I think I have found the issue produces itself only if the cascaded entity has a automatic Generated Id. What happens is that, when persisting or merging an entity with a @OneToOne to an entity with auto generated ID, the id is not updated in the object. Therefore, when you try to delete the parent entity, the child is not deleted correctly, because it is missing the id. If you replace your autogenerated ID in the child entity with a manual ID, all works fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira