| Summary: | Interface listed in persistence.xml leads to "Class cannot be resolved" validation error | ||
|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Karen Butzke <karenfbutzke> |
| Component: | JPA | Assignee: | Karen Butzke <karenfbutzke> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jolene.moffitt, neil.hauge |
| Version: | 2.3 | ||
| Target Milestone: | 3.3 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Karen Butzke
Moving JPA specific bugs to new JPA component in bugzilla. Targeting to Juno release. Probably not important enough to add a new validation error for this at this point. The bug as described has changed: 1. An enum listed in the persistence.xml class list leads to the validation error: 'Class "FooEnum" cannot be resolved' 2. An interface listed in the persistence.xml class list leads to validation errors: 'Class "FooInterface" is included in a persistence unit, but is not mapped', 'The Java class for mapped type "FooInterface" must define a non-private zero-argument constructor With my fix for this bug we have 2 new validation errors for an enum or an interface that is listed in the persistence.xml. The above validation errors should not appear anymore. 1. 'Listed class "FooEnum" must not be an enum' 2. 'Listed class "FooInterface" must not be an interface' git commit to master: http://git.eclipse.org/c/dali/webtools.dali.git/commit/?id=7d7659ab9d05c534091103aea097d10f94c6fcc0 Verified in build I-3.5.0M4-20121217201101 that the validation errors were updated correctly for enum and interface. To view steps to verify this issue go to http://wiki.eclipse.org/Dali_3.3_M4_Release |