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

Bug 288842

Summary:	Bad instanceClass for "Container" MetaClass
Product:	[Modeling] EMF	Reporter:	Bouchet Stéphane <sbouchet>
Component:	Core	Assignee:	Ed Merks <Ed.Merks>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	critical
Priority:	P3	CC:	goulwen.lefur, laurent.goubet
Version:	2.5.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Bouchet Stéphane

2009-09-08 12:13:01 EDT

Hi,

in the case we have a "Container" metaClass in our metamodel, generation is Ok, but the following code :

eobject.eClass().getInstanceClassName() 

always returns "org.eclipse.emf.ecore.impl.MinimalEObjectImpl$Container" instead of the real qualified name of the metaClass.

this bug is critical because it breaks MDT OCL with expressions like oclAsType(my::Container)... 

a test case is available under the EEF project.

cheers,

Comment 1 Ed Merks

2009-09-08 17:36:48 EDT

Sounds like a problem in the generated XyzPackageImpl that could be fixed by hand, and will need another bugzilla because it's not in EMF.  Fixing the generator itself doesn't seem critical.  In fact, when I try to reproduce this I get
   initEClass(containerEClass, com.example.library.Container.class,

So I can't even reproduce it.  Please provide an example.

Comment 2 Ed Merks

2009-09-09 10:33:20 EDT

I'm going to assume this is a duplicate given that I can't reproduce it with the latest code base.

*** This bug has been marked as a duplicate of bug 262382 ***