Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347865

Summary:	Join columns strategy ui issues of one-to-many mapping
Product:	[WebTools] Dali JPA Tools	Reporter:	Nan Li <nan.n.li>
Component:	JPA	Assignee:	Neil Hauge <neil.hauge>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	karenfbutzke, neil.hauge
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Nan Li

2011-05-31 17:07:16 EDT

Build Identifier: I20110525-0800

1. Define a one-to-many mapping
2. Go to Joining Strategy and select Join columns -> Result 1
3. Select Override default checkbox -> Result 2
4. Try to add one join column by clicking Add button -> Result 3

Result 1: The "Override default" checkbox by default is selected which is incorrect. The initial state of the checkbox should be unchecked.
Result 2: The join strategy switches from join columns to join table which is incorrect.
Result 3: The default join column is changed from something like "Default(foo_Id) -> Defult(Id)" to "Default(null) -> Defult(null)".

Reproducible: Always

Comment 1 Neil Hauge

2011-07-01 16:24:42 EDT

Moving JPA specific bugs to new JPA component in bugzilla.

Comment 2 Karen Butzke

2012-05-03 10:12:36 EDT

I think results 1 and 2 can be covered by bug 378306. I will leave this bug open to fix the remaining issue. Potentially when the user add a join column we could fully specify the the original empty @JoinColumn. This might also be affected by supporting multiple default join columns in EclipseLink