[OPENJPA-1128] Collocation constraint in case of OneToOne unidirectional Eager join.

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.0
• Component/s: slice
• Environment: Windows, openjpa 2.0.0
• Patch Info: Patch Available
• Assignee: Unassigned
• Reporter: Ashish Paliwal
• Created: 07/Jun/09 19:33
• Updated: 09/Mar/10 18:42

Description

In case of OneToOne eager unidirectional join, collocation constraint holds currently. This means, say we have 2 entities Person and Address, then both Person and its related address needs to be in the same slice.
This feature is to remove this restriction in case of OneToOne eager unidirectional join.