Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331475 - The generic type 'EIntegerObject' is not a valid substitution for type parameter 'T extends XComparable<T>'
Summary: The generic type 'EIntegerObject' is not a valid substitution for type parame...
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ed Merks CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-30 16:05 EST by Stephan Zehrer CLA
Modified: 2011-06-02 11:40 EDT (History)
0 users

See Also:

Attachments
Sample ecore for to demonstrate the problem. (1.27 KB, application/xml)
2010-11-30 16:07 EST, Stephan Zehrer CLA 		no flags Details
View All 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 Stephan Zehrer CLA 2010-11-30 16:05:32 EST 
Build Identifier: 20100917-0705

You will get this Valvation error if you generate a genmodel of the attached ecore file.
Comment for Ed:
 > This is the idea, but there is the next problem, if i try to bind the 
> T to e.g. an Integer Class or EIntegerObject
> I get a error something about "not valid substitution". Seems he 
> know's nothing about the comparable interface.
Oh.  That's not good.  With an EDataType, EMF can't know whether it's 
valid with respect to the bound so it should assume it's valid.  Please 
open a bugzilla with that case... 

Maybe a duplicate to Bug 273142

Reproducible: Always

Steps to Reproduce:
1. generate genmode from the attached ecore file.
Comment 1 Stephan Zehrer CLA 2010-11-30 16:07:31 EST 
Created attachment 184184 [details]
Sample ecore for to demonstrate the problem.
Comment 2 Ed Merks CLA 2011-05-13 11:08:27 EDT 
A fix is committed to CVS for EMF 2.7.
Comment 3 Ed Merks CLA 2011-06-02 11:40:15 EDT 
The fix is available in 3.7RC3 and later.