| Summary: | [Validation] Caching validation warnings | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Leslie Davis <les.davis> | ||||
| Component: | JPA | Assignee: | Neil Hauge <neil.hauge> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | karenfbutzke, neil.hauge | ||||
| Version: | 3.0 | ||||||
| Target Milestone: | Future | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Leslie Davis
Created attachment 190442 [details]
proposed bug fix patch
Moving JPA specific bugs to new JPA component in bugzilla. Since this already has a patch, should we get it in for M2? Targeting to M2 so we see it 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) This validation has been complicated by EclipseLink's multitenancy feature. Deferring this bug to the future. |