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

Bug 368156

Summary:	[Validation] JPA supports only List, Set, Map, and Collection for collection mappings
Product:	[WebTools] Dali JPA Tools	Reporter:	Karen Butzke <karenfbutzke>
Component:	JPA	Assignee:	Karen Butzke <karenfbutzke>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	neil.hauge
Version:	3.1
Target Milestone:	3.2 M6
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	372904

Description Karen Butzke

2012-01-09 08:32:34 EST

JPA supports only List, Set, Map, and Collection types for collection mappings. 

EclipseLink supports other types if EAGER fetching is used. If LAZY fetching is used then EclipseLink needs to be able to weave.

see bug 367122

Comment 1 Karen Butzke

2012-02-29 15:26:21 EST

These can exist on any collection mappings whether the attribute type is
defined by the java attribute or in the case of a VIRTUAL mapping defined by
the attribute-type:
1. The attribute type for a collection mapping must be java.util.Collection,
java.util.Set, java.util.List or java.util.Map
2. In implied attribute [attribute name], the attribute type for a collection
mapping must be java.util.Collection, java.util.Set, java.util.List or
java.util.Map

Currently the validation only looks that the attribute type implements
Collection, Set, List, or Map. I have opened bug 372904 for validation that
checks that the attribute type *is* Collection, Set, List, or Map.