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

Bug 323468

Summary:	Inconsistent EEList model for EObject.eInvoke
Product:	[Modeling] EMF	Reporter:	Ed Willink <ed>
Component:	Core	Assignee:	Ed Merks <Ed.Merks>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.6.0
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Ed Willink

2010-08-24 04:34:33 EDT

All self references in Ecore.ecore use the "#//..." href form except:

    <eOperations name="eInvoke" eType="#//EJavaObject" eExceptions="#//EInvocationTargetException">
      <eParameters name="operation" eType="#//EOperation"/>
      <eParameters name="arguments">
        <eGenericType eClassifier="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EEList">
          <eTypeArguments/>
        </eGenericType>
      </eParameters>
    </eOperations>

Presumably a typo for

        <eGenericType eClassifier="#//EEList">

Comment 1 Ed Merks

2010-08-24 12:17:16 EDT

The fix is committed to CVS for 2.7.

Comment 2 Ed Willink

2010-08-25 03:05:28 EDT

2.6.1?

Comment 3 Ed Merks

2010-08-25 09:33:08 EDT

It strikes me as trivial issue not worth addressing in the maintenance stream, no?

Comment 4 Ed Willink

2010-08-25 12:19:10 EDT

It's certainly trivial, which makes it very safe to include in 2.6.1.

The bug was introduced in 2.6.0 so it seems desirable to limit its lifetime to 3 months rather than a year plus.

The bug manifests itself if Ecore.ecore is loaded, since EEList is then resolved in another variant of Ecore. Not a common activity, but a very easy fix.

Comment 5 Ed Merks

2010-11-05 05:41:33 EDT

The fix is available in the latest build for the stream.