| [ATL] Datatype mapping during Ecore to KM3 extraction [message #376938] |
Wed, 02 May 2007 16:00  |
Eclipse User |
|
|
|
Originally posted by: quentin.glineur.obeo.fr
Hi,
I am wondering if it is possible to parametrize the process of
extraction of an ecore metamodel to KM3 so that to obtain a "regular"
km3 file ? By "regular", I mean having types mapped (for example from
EString to String) and a package named "PimitiveTypes" with ocl
datatypes instead of a package named "ecore" with ecore datatypes.
Best regards,
Quentin
|
|
|
| Re: [ATL] Datatype mapping during Ecore to KM3 extraction [message #376940 is a reply to message #376938] |
Wed, 02 May 2007 17:05  |
 Frédéric Jouault
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
Hello,
Please, ask your future ATL-related questions on the
eclipse.modeling.m2m newsgroup. As a matter of fact, ATL has moved from
the GMT to the M2M project.
I added the eclipse.modeling.m2m newsgroup in copy of my answer, so that
you can directly reply to this message.
To answer your question:
You can automatize the process of extracting an Ecore metamodel to a KM3
file using either of these two main options:
- using an ant script (preferred method, see:
http://wiki.eclipse.org/index.php/AM3_Ant_Tasks),
- using Java code calling the KM3Projector class of the KM3 plugin.
To do things that the EMF2KM3.atl (i.e., Ecore-to-KM3) transformation
does not do yet (e.g., primitive types mapping), you can modify the
EMF2KM3.atl file available from:
http://www.eclipse.org/m2m/atl/atlTransformations/#EMF2KM3
Do not hesitate to contribute your modifications using Bugzilla.
Such a contribution to this very same transformation has already been
made (see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=156446).
Regards,
Frédéric Jouault
Quentin Glineur wrote:
> Hi,
>
> I am wondering if it is possible to parametrize the process of
> extraction of an ecore metamodel to KM3 so that to obtain a "regular"
> km3 file ? By "regular", I mean having types mapped (for example from
> EString to String) and a package named "PimitiveTypes" with ocl
> datatypes instead of a package named "ecore" with ecore datatypes.
>
> Best regards,
>
> Quentin
|
|
|
| Re: [ATL] Datatype mapping during Ecore to KM3 extraction [message #581652 is a reply to message #376938] |
Wed, 02 May 2007 17:05 |
Frédéric Jouault
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
Hello,
Please, ask your future ATL-related questions on the
eclipse.modeling.m2m newsgroup. As a matter of fact, ATL has moved from
the GMT to the M2M project.
I added the eclipse.modeling.m2m newsgroup in copy of my answer, so that
you can directly reply to this message.
To answer your question:
You can automatize the process of extracting an Ecore metamodel to a KM3
file using either of these two main options:
- using an ant script (preferred method, see:
http://wiki.eclipse.org/index.php/AM3_Ant_Tasks),
- using Java code calling the KM3Projector class of the KM3 plugin.
To do things that the EMF2KM3.atl (i.e., Ecore-to-KM3) transformation
does not do yet (e.g., primitive types mapping), you can modify the
EMF2KM3.atl file available from:
http://www.eclipse.org/m2m/atl/atlTransformations/#EMF2KM3
Do not hesitate to contribute your modifications using Bugzilla.
Such a contribution to this very same transformation has already been
made (see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=156446).
Regards,
Frédéric Jouault
Quentin Glineur wrote:
> Hi,
>
> I am wondering if it is possible to parametrize the process of
> extraction of an ecore metamodel to KM3 so that to obtain a "regular"
> km3 file ? By "regular", I mean having types mapped (for example from
> EString to String) and a package named "PimitiveTypes" with ocl
> datatypes instead of a package named "ecore" with ecore datatypes.
>
> Best regards,
>
> Quentin
|
|
|
Powered by
FUDForum. Page generated in 0.01898 seconds
] 
Search
Help
Register
Login
Home
