[
https://issues.apache.org/jira/browse/OPENJPA-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-1964.
--------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: Seen only inside the abandoned
hector-jpa CassandraStoreManager (its repo test is the only reproducer). No
JDBC case was given, and cascade persist on master's kernel is covered by the
TCK. Please reopen if this still happens with OpenJPA 4.x.
> 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 was sent by Atlassian Jira
(v10.3.26#10030026)
