Bugzilla – Full Text Bug Listing
| Summary: | Validation error when no access defined in orm.xml type mapping | ||
|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Karen Butzke <karenfbutzke> |
| Component: | JPA | Assignee: | Neil Hauge <neil.hauge> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | neil.hauge, vyemialyanchyk |
| Version: | 2.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Moving JPA specific bugs to new JPA component in bugzilla. |
From the spec section 2.3.1: It is an error if a default access type cannot be determined and an access type is not explicitly specified by means of annotations or the XML descriptor. We need a validation error if a type mapping does not specify an access type in an orm.xml file of the Generic platform. The type mapping could define no access type as long as all the attribute mappings do define an access type. This is only for the case where no access is defined in the java(or defaulted via annotation placement) or in the orm.xml or persistence unit defaults. We would not want a validation error for the EclipseLink platform it default to FIELD in this case.