[
https://issues.apache.org/jira/browse/OPENJPA-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691986#comment-13691986
]
Eslam Nawara commented on OPENJPA-1964:
---------------------------------------
Is there any plan for resolution on this bug. We are facing the same problem
stated above
> Cascade on persist does not correctly cascade all objects in the graph
> ----------------------------------------------------------------------
>
> Key: OPENJPA-1964
> URL: https://issues.apache.org/jira/browse/OPENJPA-1964
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.1.0
> Environment: Sun JDK 1.6
> Reporter: Todd Nine
> Priority: Blocker
>
> We're currently building a Cassandra adapter for OpenJPA. In doing so we've
> encountered an issue that I think may be a bug. We have our test cases and
> source available here.
> https://github.com/riptano/hector-jpa/blob/master/src/test/java/com/datastax/hectorjpa/store/ManyToManyIndexTest.java
> Essentially, the test constructs the following relationships.
> User A -one-many--> Observe -many-one--> User B
> Essentially our test models what is functionally a many-many with additional
> meta.
> When CassandraStoreManager.flush is called only UserA and Observe are in the
> pNew collection. Where User A, Observer and User B should be in pNew since
> all cascade on persist.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
