[
https://issues.apache.org/jira/browse/OPENJPA-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-1982.
--------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: A design question raised for the
abandoned hector-jpa CassandraStoreManager, with no JDBC reproducer and nothing
concrete to act on. Please reopen if this still happens with OpenJPA 4.x.
> StateManager.fetchObjectId() does not correctly cascade when using a non JDBC
> store
> -----------------------------------------------------------------------------------
>
> Key: OPENJPA-1982
> URL: https://issues.apache.org/jira/browse/OPENJPA-1982
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 2.1.0
> Environment: Ubuntu Sun java 10.6
> Reporter: Todd Nine
> Priority: Blocker
>
> Test case
> https://github.com/riptano/hector-jpa/blob/compositeentityid/src/test/java/com/datastax/hectorjpa/store/ManyToOneIndexTest.java
> : basicFollowingPersistence
> Store implementation:
> https://github.com/riptano/hector-jpa/blob/compositeentityid/src/main/java/com/datastax/hectorjpa/store/CassandraStoreManager.java
> When cascading objects for collections, the flush and cascading of the
> objectId is not correctly set when a combination of @Entity and @Id
> annotations are used to create a composite entity. The flush dependency
> requirements are currently undocumented for StoreManagers. Is this the
> responsibility of the kernel to flush Entities in dependency order or the
> responsibility of the implementing StoreManager?
>
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
