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

Bug 369944

Summary:	[EclipseLink] dynamic persistence and extensible entities validation for attribute-type
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	Keywords:	plan
Target Milestone:	3.2 M6
Hardware:	PC
OS:	Windows XP
Whiteboard:	EclipseLink
Bug Depends on:
Bug Blocks:	309475

Description Karen Butzke

2012-01-27 10:27:32 EST

EclipseLink dynamic persistence and extensible entities use the attribute-type attribute on VIRTUAL mappings. We need to validate that attribute-type has been specified for an attribute mapping with an access type of VIRTUAL. Also validate that the attribute-type is a valid type on the classpath or another dynamic type. We could have xml code completion for this attribute. The package element is used in conjunction with attribute-type.

Comment 1 Karen Butzke

2012-02-29 15:26:52 EST

Added the following validation:
These can exist EclipseLink attribute that has a specified or default access type of VIRTUAL:
1. Virtual attribute [attribute name] must specify an attribute-type
2. Attribute type [class name] does not exist

These were added to 1-m, m-m and element collection mappings if they define a map key class
3. Map key class [class name] is not an entity, embeddable or basic type
4. In implied attribute [attribute name], map key class [class name] is not an entity, embeddable or basic type

This was added for embedded or embedded-id mappings, there was no validation for an implied attribute:
5. In implied attribute [attribute name], [class name] is not mapped as an embeddable