Eclipse Community Forums: EMF » [Edapt] Factory problems ...

Home » Modeling » EMF » [Edapt] Factory problems ...

[Edapt] Factory problems ... [message #1028585]

Thu, 28 March 2013 09:06

Eclipse User

Hi,

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 ?

Thanks !

[Updated on: Thu, 28 March 2013 09:33] by Moderator

Re: [Edapt] Factory problems ... [message #1029166 is a reply to message #1028585]

Fri, 29 March 2013 04:44

Eclipse User

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 DynamicEObject.

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 ...

Re: [Edapt] Factory problems ... [message #1059608 is a reply to message #1029166]

Mon, 20 May 2013 15:27

Eclipse User

Did you ever get an answer to this problem?

We are having the same issue.

Thanks in advance,

Jim

Re: [Edapt] Factory problems ... [message #1059805 is a reply to message #1029166]

Tue, 21 May 2013 12:35

Eclipse User

Do you ever find a solution to this problem?

I'm having the same issue.

Thanks

Re: [Edapt] Factory problems ... [message #1059940 is a reply to message #1029166]

Wed, 22 May 2013 05:00

Eclipse User

Hi,

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
this.
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.

Cheers,
Maximilian

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
> DynamicEObject.
>
> 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 ...

--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich

Previous Topic:	How to resolve this error?
Next Topic:	Customize EMF Enums

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 15 23:55:05 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter