Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350180 - [EclipseLink] eclipselink_oxm_2_3.xsd is not up to date
Summary: [EclipseLink] eclipselink_oxm_2_3.xsd is not up to date
Status: CLOSED DUPLICATE of bug 349071
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: dali.general-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-23 14:56 EDT by Blaise Doughan CLA
Modified: 2011-06-27 17:29 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blaise Doughan CLA 2011-06-23 14:56:36 EDT
A pre-release version of the eclipselink_oxm_2_3.xsd schema was registered with the Eclipse XML catalog and needs to be updated to the released version.
Comment 1 Paul Fullbright CLA 2011-06-23 15:10:52 EDT
May likely extend to other eclipselink schemas.
Comment 2 Paul Fullbright CLA 2011-06-23 15:28:39 EDT
Lumping this in with bug 349071

*** This bug has been marked as a duplicate of bug 349071 ***
Comment 3 Neil Hauge CLA 2011-06-24 17:04:48 EDT
Workaround:

In the XML Catalog add a "user specified entry" for the schema with the same key name as the "plugin specified entry" (http://www.eclipse.org/eclipselink/xsds/eclipselink_oxm_2_3.xsd) and point this 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 4 Neil Hauge CLA 2011-06-27 17:29:01 EDT
Workaround:

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 #3 doesn't work.