| Importing Rose Model with OCL Constraints? [message #63641] |
Wed, 29 October 2008 12:44  |
Eclipse User |
|
|
|
Hi,
we have a metamodel in Rose that has OCL constraints modeled as defined by
the Unisys MOF profile as supported by the Unisys add-in for exporting
Rose models to MOF XMI. In particular, the profile says that constraints
on a class are modeled as nested classes with stereotype <<constraint>>,
containing an operation whose name maps to the attribute "language" and
whose contents on the "Semantics" tab map to the "expression" attribute.
Would the EMF Rose import by any chance allow us to import these hundreds
of constraints we have expressed this way into a set of constraints over
an Ecore metamodel?
Thanks and best,
-- Axel
|
|
|
| Re: Importing Rose Model with OCL Constraints? [message #63665 is a reply to message #63641] |
Wed, 29 October 2008 13:14  |
| Eclipse User |
|
|
|
Originally posted by: cdamus.zeligsoft.com
Hi, Axel,
This is an EMF question, so I'm replying to that newsgroup.
As far as I know, the Rose importer is not, itself, extensible by
clients (or, at least, not intended to be). I could be wrong. Ed?
I should think, though, that it wouldn't be difficult to tweak the
original to make it recognize your constraint structure. I don't know
enough about the EMF model importers, though, to give a coherent answer.
Cheers,
Christian
Axel Uhl wrote:
> Hi,
>
> we have a metamodel in Rose that has OCL constraints modeled as defined
> by the Unisys MOF profile as supported by the Unisys add-in for
> exporting Rose models to MOF XMI. In particular, the profile says that
> constraints on a class are modeled as nested classes with stereotype
> <<constraint>>, containing an operation whose name maps to the attribute
> "language" and whose contents on the "Semantics" tab map to the
> "expression" attribute.
>
> Would the EMF Rose import by any chance allow us to import these
> hundreds of constraints we have expressed this way into a set of
> constraints over an Ecore metamodel?
>
> Thanks and best,
> -- Axel
>
|
|
|
| Re: Importing Rose Model with OCL Constraints? [message #63686 is a reply to message #63665] |
Wed, 29 October 2008 13:26 |
| Eclipse User |
|
|
|
Christian,
Comments below.
Christian W. Damus wrote:
> Hi, Axel,
>
> This is an EMF question, so I'm replying to that newsgroup.
>
> As far as I know, the Rose importer is not, itself, extensible by
> clients (or, at least, not intended to be). I could be wrong. Ed?
Of course there's nothing stopping folks from extending RoseEcoreBuilder
and related classes. They're unlikely to change significantly ever
again. The JavaEcoreBuilder was changed in binary incompatible ways in
the past.
>
> I should think, though, that it wouldn't be difficult to tweak the
> original to make it recognize your constraint structure. I don't know
> enough about the EMF model importers, though, to give a coherent answer.
I imagine RoseEcoreBuilder could be tweaked to filter out these cases
and do something special with them. Probably it's a lot of work.
>
> Cheers,
>
> Christian
>
>
> Axel Uhl wrote:
>> Hi,
>>
>> we have a metamodel in Rose that has OCL constraints modeled as
>> defined by the Unisys MOF profile as supported by the Unisys add-in
>> for exporting Rose models to MOF XMI. In particular, the profile says
>> that constraints on a class are modeled as nested classes with
>> stereotype <<constraint>>, containing an operation whose name maps to
>> the attribute "language" and whose contents on the "Semantics" tab
>> map to the "expression" attribute.
>>
>> Would the EMF Rose import by any chance allow us to import these
>> hundreds of constraints we have expressed this way into a set of
>> constraints over an Ecore metamodel?
>>
>> Thanks and best,
>> -- Axel
>>
|
|
|
Powered by
FUDForum. Page generated in 0.68364 seconds
Home