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

Bug 350180

Summary:	[EclipseLink] eclipselink_oxm_2_3.xsd is not up to date
Product:	[WebTools] Dali JPA Tools	Reporter:	Blaise Doughan <blaise.doughan>
Component:	General	Assignee:	dali.general-inbox <dali.general-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	neil.hauge, paul.fullbright
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=349071
Whiteboard:

Description Blaise Doughan

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

2011-06-23 15:10:52 EDT

May likely extend to other eclipselink schemas.

Comment 2 Paul Fullbright

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

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

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.