Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323527 - [Validation] Mapping annotations applied to both persistent fields and properties without Access defined
Summary: [Validation] Mapping annotations applied to both persistent fields and proper...
Status: NEW
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: JPA (show other bugs)
Version: 3.0   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-08-24 13:42 EDT by Karen Butzke CLA
Modified: 2013-09-06 16:38 EDT (History)
1 user (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-08-24 13:42:48 EDT 
If mapping annotations are applied to both persistent field and properties of a java entity without access type defined there should be a validation error.
Comment 1 Neil Hauge CLA 2011-07-01 16:26:12 EDT 
Moving JPA specific bugs to new JPA component in bugzilla.
Comment 2 Karen Butzke CLA 2012-09-04 14:28:22 EDT 
This validation should be easier to implement now that we pull all the annotated fields and properties into the context model.

There was also a recent Stack Overflow question where the user had a validation error they couldn't figure out because of mixed access. http://stackoverflow.com/questions/12135233/entity-not-recognizing-the-id-in-a-mappedsuperclass/12183505#12183505