Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323674 - "Cannot find compatible feature" in synonym URIs
Summary: "Cannot find compatible feature" in synonym URIs
Status: CLOSED WORKSFORME
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 1.0.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-26 01:41 EDT by Ed Willink CLA
Modified: 2017-09-19 17:34 EDT (History)
2 users (show)

See Also:
sebastian.zarnekow: indigo+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2010-08-26 01:41:51 EDT 
A grammar segment such as

import "platform:/resource/org.eclipse.ocl.examples.xtext.base/model/BaseCST.ecore" as base
import "platform:/resource/org.eclipse.ocl.examples.pivot/model/pivot.ecore" as pivot
generate myDsl "http://www.xtext.org/example/mydsl1/MyDsl"

...

Greeting  returns base::QualifiedTypeRefCS:
	'Hello' namespace=[pivot::Namespace|ID] '!';

fails with a "Cannot find compatible feature" in "in sealed EClass"

when the relevant 'namespace' declaration in BaseCST.ecore is:

    <eStructuralFeatures xsi:type="ecore:EReference" name="namespace" eType="ecore:EClass ../../org.eclipse.ocl.examples.pivot/model/pivot.ecore#//Namespace"/>

which is the default EMF usage. The problem is cured by changing to:

    <eStructuralFeatures xsi:type="ecore:EReference" name="namespace" eType="ecore:EClass platform:/resource/org.eclipse.ocl.examples.pivot/model/pivot.ecore#//Namespace"/>

It seems the models are being compared by unresolved URI rather than resolved physical location.
Comment 1 Sebastian Zarnekow CLA 2011-01-10 10:22:27 EST 
Scheduled for M5 as grammar mixin and Ecore import will become more popular
with Xbase.
Comment 2 Sebastian Zarnekow CLA 2011-02-07 11:11:09 EST 
Cannot reproduce this one. Please reopen if the problem persists in Xtext 2.0
Comment 3 Ed Willink CLA 2011-02-07 11:51:31 EST 
These URI problems are evil; confusing, poorly diagnosed and unstable.

I think that my Xtext build problems have gone away with M5. Now that I always build with MWE scripts, maybe the Eclipse running/not-running hazards are not provoked.
Comment 4 Sebastian Zarnekow CLA 2011-02-07 12:38:19 EST 
(In reply to comment #2)
> Cannot reproduce this one. 

Tested in editor context, builder context and in mwe2 workflow.
Comment 5 Karsten Thoms CLA 2017-09-19 17:23:06 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 6 Karsten Thoms CLA 2017-09-19 17:34:27 EDT 
Closing all bugs that were set to RESOLVED before Neon.0