Eclipse Community Forums: Modeling (top-level project) » Ecore: best practice for unmodelled "references"?

Home » Modeling » Modeling (top-level project) » Ecore: best practice for unmodelled "references"?(What's the best way to reference an unmodelled Java class?)

Show: Today's Messages :: Show Polls :: Message Navigator

Ecore: best practice for unmodelled "references"? [message #1076523]

Wed, 31 July 2013 14:17

Ed Staub

Messages: 12
Registered: July 2009

Junior Member

In Ecore, what's the best way to create a "reference" (EReference or EAttribute) to an unmodelled Java class?

Does one create a "stub" EPackage for the class's package, and import it?

This gets tedious when there are a lot of packages.
In that case, if there are multiple ecore models importing the same set of stub EPackages, does one then create a dummy super-package that imports all the others?

Report message to a moderator

Re: Ecore: best practice for unmodelled "references"? [message #1076586 is a reply to message #1076523]

Wed, 31 July 2013 15:54

Ed Merks

Messages: 29395
Registered: July 2009

Senior Member

Ed,

Please use eclipse.tools.emf for EMF questions in the future. More
comments below.

On 31/07/2013 4:17 PM, Ed Staub wrote:
> In Ecore, what's the best way to create a "reference" (EReference or
> EAttribute) to an unmodelled Java class?
You can create an EClass or EDataType and set the instanceTypeName to
the fully qualified name of the existing Java class/interface. But keep
in mind that if you create an EClass wrapper, and you use it for an
EReference's eReferenceType (as opposed to say an EClass's eSuperTypes),
the actual instance value you put into that reference must implement
EObject/InternalEObject.
> Does one create a "stub" EPackage for the class's package, and import it?
>
> This gets tedious when there are a lot of packages.
> In that case, if there are multiple ecore models importing the same
> set of stub EPackages, does one then create a dummy super-package that
> imports all the others?
You can package up your wrapper EClasses and EDataTypes and for reuse as
you see fit.

Report message to a moderator