|[Edapt] Factory problems ... [message #1028585]
||Thu, 28 March 2013 13:06
| ben ben
Registered: June 2012
I have a problem trying to migrate my model using Edapt.
It seems that Edapt doesn't use package/factory classes generated by EMF (specific for my model).
It uses generic EPackageImpl/EFactoryImpl instead.
The problem is : using theses factories, it fails (IllegalArgumentException) to create a type that has a wrapped Interface as super type (see picture).
How can I tell Edapt to use generated factories ?
[Updated on: Thu, 28 March 2013 13:33]
Report message to a moderator
|Re: [Edapt] Factory problems ... [message #1059940 is a reply to message #1029166]
||Wed, 22 May 2013 09:00
| Maximilian Koegel
Registered: July 2009
I just noticed your original request because another question was added,
sorry for the delay.
To my best knowledge the scenario you describe is not supported by Edapt
and would require changes in the Edapt code. Please open a bugzilla for
If you are not able to make a contribution but you would like the
problem solved very soon, I could get you in contact with a developer
able to make such contribution.
Am 29.03.2013 09:44, schrieb ben ben:
> Going further in think I beginning to understand how Edapt works.
> As it has to read a model which is probably not compatible with loaded
> metamodel version, it must create "generic" object, so it uses
> The problem is : I get a ClassCastException in public void eSet(int
> featureID, Object newValue)
> method becauses EMF tries to cast DynamicEObject in my model object ...
Get Professional Eclipse Support: http://eclipsesource.com/munich
Powered by FUDForum
. Page generated in 0.02828 seconds