Community
Participate
Working Groups
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
Created attachment 197954 [details] proposed patch against head
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
*** Bug 350180 has been marked as a duplicate of this bug. ***
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
checked in to HEAD for 3.0.1
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.
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.
Bug 350615 was entered as a possible solution to avoiding this particular problem in the future.
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