[jira] [Commented] (OPENJPA-1982) StateManager.fetchObjectId() does not correctly cascade when using a non JDBC store

["Rick Curtis (JIRA)" <ji...@apache.org>]

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

Rick Curtis commented on OPENJPA-1982:
--------------------------------------

You said that this doesn't work properly with a non-JDBC store... have you confirmed how this behaves with the JDBC backend? 

Could I get you to write an OpenJPA test that would drop into our build?

Thanks,
Rick

> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira