Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317848 - Validation error when no access defined in orm.xml type mapping
Summary: Validation error when no access defined in orm.xml type mapping
Status: NEW
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: JPA (show other bugs)
Version: 2.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Neil Hauge CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-24 11:42 EDT by Karen Butzke CLA
Modified: 2013-09-06 16:23 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karen Butzke CLA 2010-06-24 11:42:57 EDT 
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.
Comment 1 Neil Hauge CLA 2011-07-01 16:24:06 EDT 
Moving JPA specific bugs to new JPA component in bugzilla.