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

Bug 354676

Summary:

[Validation][JPA2.0] MapKeyClass validation needed for 1-m and m-m mappings

Product:

[WebTools] Dali JPA Tools

Reporter:

Karen Butzke <karenfbutzke>

Component:

JPA

Assignee:

Karen Butzke <karenfbutzke>

Status:

VERIFIED FIXED

QA Contact:

Severity:

enhancement

Priority:

CC:

jolene.moffitt

Version:

3.0

Keywords:

plan

Target Milestone:

3.1 M2

Hardware:

OS:

Windows XP

Whiteboard:

JPA2.0

Attachments:

Description	Flags
test project	none

Description Karen Butzke

2011-08-12 17:22:16 EDT

We have MapKeyClass validation on an element collection mapping, we need to add the same validation to 1-m and m-m mappings including orm.xml virtuals

Comment 1 Karen Butzke

2011-08-25 16:28:11 EDT

added validation to java 1-m and m-m:
1. Map key class not defined
2. In implied attribute <attribute-name>, map key class not defined

added validation to orm 1-m and m-m:
1. Map key class not defined.
2. Map key class does not exist on the project classpath.

Same validation exists for element collections in java and orm and for the target-class element.

Also added validation for target-entity in orm for:
1. Target entity does not exist on the project classpath

Comment 2 Karen Butzke

2011-08-25 16:30:21 EDT

fixed in 3.1M2

Comment 3 Karen Butzke

2011-09-29 12:10:57 EDT

Created attachment 204310 [details]
test project

I've attached a test project that shows an element collection with both the "Map key class is not defined" and "Target class is not defined" validation errors.

Comment 4 Jolene Moffitt

2011-10-05 08:03:24 EDT

Verified in Build I-3.4.0-20110922230524 

Verified map key class validation was added. See the link to view test steps for verification. http://wiki.eclipse.org/Dali_3.1_M2