You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "eugene (JIRA)" <ji...@apache.org> on 2009/08/03 12:21:14 UTC

[jira] Commented: (OPENJPA-1219) CLONE -Unexpected mere-cascade behavior when cascade.all/merge specified on both sides of relationships !!!

    [ https://issues.apache.org/jira/browse/OPENJPA-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738265#action_12738265 ] 

eugene commented on OPENJPA-1219:
---------------------------------

My test units works fine with OpenEJB 3.1.1 with OpenJPA 1.3, but if i run standalone OpenEJB server , the pboblem appear again.

> CLONE -Unexpected mere-cascade behavior when cascade.all/merge specified on both sides of relationships !!!
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1219
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1219
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 1.2.0, 2.0.0-M2
>            Reporter: eugene
>             Fix For: 1.3.0, 2.0.0-M2
>
>
> When cascade.all/merge is specified on both sides of relationships, and if the parent is attached and the children are newly created entities that are being merged, the merge is not cascading to the parent's relationships if the parent is attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.