Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338249 - [Validation] Caching validation warnings
Summary: [Validation] Caching validation warnings
Status: NEW
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: JPA (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Neil Hauge CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-25 12:29 EST by Leslie Davis CLA
Modified: 2011-10-21 14:35 EDT (History)
2 users (show)

See Also:

Attachments
proposed bug fix patch (13.89 KB, patch)
2011-03-04 16:06 EST, Leslie Davis CLA 		no flags Details | Diff
View All 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 Leslie Davis CLA 2011-02-25 12:29:09 EST 
1.  If shared-cache-mode is set to anything other than ENABLE_SELECTIVE or DISABLE_SELECTIVE we should have a validation warning anywhere the @Cacheable  annotation and its XML equivalent is used indicating that the setting is ignored. 

2.  If you define the @Cache annotation or its XML equivalent on an inheritance subclass, the annotation will be ignored so we should have a validation warning indicating as such.
Comment 1 Leslie Davis CLA 2011-03-04 16:06:33 EST 
Created attachment 190442 [details]
proposed bug fix patch
Comment 2 Neil Hauge CLA 2011-07-01 16:27:00 EDT 
Moving JPA specific bugs to new JPA component in bugzilla.
Comment 3 Karen Butzke CLA 2011-08-15 16:15:32 EDT 
Since this already has a patch, should we get it in for M2? Targeting to M2 so we see it
Comment 4 Karen Butzke CLA 2011-08-17 07:39:02 EDT 
The SUPER_TYPE_SPECIFIES_CACHE_CHILD_SETTING_WILL_BE_IGNORED validation does not take into account mixed java and xml specification. So a java entity could have an orm.xml entity as its parent and vice versa. In these cases no validation error would be given if the cache setting was specified in the parent.

This also needs to be added to the validation preferences (JpaProblemSeveritiesPage)
Comment 5 Karen Butzke CLA 2011-10-21 14:35:07 EDT 
This validation has been complicated by EclipseLink's multitenancy feature. Deferring this bug to the future.