Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 349071

Summary: [EclipseLink] eclipselink 2.3 schemas not up to date
Product: [WebTools] Dali JPA Tools Reporter: Karen Butzke <karenfbutzke>
Component: GeneralAssignee: Karen Butzke <karenfbutzke>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P1 CC: blaise.doughan, jolene.moffitt, neil.hauge, paul.fullbright
Version: 3.0Flags: neil.hauge: review+
Target Milestone: 3.0.1   
Hardware: PC   
OS: Windows XP   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=350180
Whiteboard: fix_ready
Attachments:
Description Flags
proposed patch against head
none
another proposed patch against head none

Description Karen Butzke CLA 2011-06-10 12:25:12 EDT
The eclipselink-orm.xml schema included in org.eclipse.jpt.common.eclipselink.core is not up to date with the latest changes in eclipselink 2.3. Multi-tenant support was added in May 2011
Comment 1 Karen Butzke CLA 2011-06-14 10:18:43 EDT
Created attachment 197954 [details]
proposed patch against head
Comment 2 Paul Fullbright CLA 2011-06-23 15:28:02 EDT
Actually, I'm going to go ahead and lump all eclipselink 2.3 schemas under one bug.

This includes (or could potentially include):

eclipselink_orm_2_3.xsd
eclipselink_oxm_2_3.xsd
eclipselink_persistence_map_2_3.xsd
Comment 3 Paul Fullbright CLA 2011-06-23 15:28:39 EDT
*** Bug 350180 has been marked as a duplicate of this bug. ***
Comment 4 Karen Butzke CLA 2011-06-24 09:10:48 EDT
Created attachment 198529 [details]
another proposed patch against head

This patch includes an update to the eclipselink_persistence_map_2.3.xsd. All 3 schemas have been updated. The translators for the 2.3 orm schema have been updated to fix some issues with not having translators for all elements
Comment 5 Karen Butzke CLA 2011-06-24 11:50:03 EDT
checked in to HEAD for 3.0.1
Comment 6 Neil Hauge CLA 2011-06-27 17:31:37 EDT
Workaround:

In the XML Catalog add a "user specified entry" for the out-of-date schema with the same key name as the "plugin specified entry" (For example  - "http://www.eclipse.org/eclipselink/xsds/eclipselink_oxm_2_3.xsd" in the case of the OXM schema) and point this entry to the shipped schema from the EclipseLink install.

The user entry will then override the plugin entry and you will get validation
and content assist based on the user defined schema.
Comment 7 Neil Hauge CLA 2011-06-27 17:32:19 EDT
Workaround 2:

Another workaround is to manually replace the out-of-date schema included in
the org.eclipse.jpt.common.eclipselink.core_1.0.0.jar /schemas directory.  This
workaround should be used if the workaround in comment #6 doesn't work.
Comment 8 Neil Hauge CLA 2011-06-28 14:33:48 EDT
Bug 350615 was entered as a possible solution to avoiding this particular problem in the future.
Comment 9 Jolene Moffitt CLA 2011-08-02 14:11:48 EDT
Verified in Build I-3.4.0-20110731180834

Verified the build has the latest eclipselink_orm_2_3.xsd, eclipselink_oxm_2_3.xsd, eclipselink_persistence_map_2_3.xsd files.  See the link to view test steps for verification. http://wiki.eclipse.org/Dali_3.0.1