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

• Type: Bug
• Status: Open
• Priority: Blocker
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Component/s: kernel
• Environment: Ubuntu Sun java 10.6
• Assignee: Unassigned
• Reporter: Todd Nine
• Created: 18/Apr/11 00:34
• Updated: 19/Apr/11 21:12

Description

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?