I have just started writing a simple UML model
(by using TOPCASED TOOLS) and convert it to
ecore. A problem I met is that a UML element
of Association is not converted to an EMF element
but it just disappears.

The model is really simple. There's two classes
(say Class1 and Class2) and they have an association
between them. (*)

In order to convert it to ecore model, I used the
eclipse (3.3) wizard to create a new EMF model from UML.
In the generated .ecore file (**), there's no element
(I expect EReference obviously) which is converted
from the uml:Association.

I guess uml:Association should be converted to
ecore:EReference in the procedure and there was
something wrong somewhere.

Please let me know how to do correctly.

Thanks in advance.

(*) The association is serialized like the following.
(The "xmi:id"s are converted by hand for this message.)

Both of the association ends are owned by the association, which means that
when the model is mapped to EMOF (Ecore), the properties will be lost. In
order to preserve an association end, the property representing it needs to
be owned by the end type (i.e. the class).

Toshinao,
I took a quick look at TopCased a few months ago, and it appeared that they
alway model navigable associations by using the alternative UML
representation where navigable ends are owned by the Association, instead of
owned by the source class (as indicated by Kenn). Both are valid UML
representations, but for code generation from the model I think that tools
should use the Class owned navigable ends by default. This is a key reason
why I chose not to look at TopCased beyond my initial review...

Regards,
Dave Carlson

"Kenn Hussey" <khussey@ca.ibm.com> wrote in message
news:f8lemd$70k$1@build.eclipse.org...
> Toshinao,
>
> Both of the association ends are owned by the association, which means
> that when the model is mapped to EMOF (Ecore), the properties will be
> lost. In order to preserve an association end, the property representing
> it needs to be owned by the end type (i.e. the class).
>
> Kenn
>
> "Toshinao Ishii" <i_j_e_x_a@yahoo.co.jp> wrote in message
> news:f8lckb$lj6$1@build.eclipse.org...
>> Hi.
>>
>> I have just started writing a simple UML model
>> (by using TOPCASED TOOLS) and convert it to
>> ecore. A problem I met is that a UML element
>> of Association is not converted to an EMF element
>> but it just disappears.

Dave Carlson wrote:
> Toshinao,
> I took a quick look at TopCased a few months ago, and it appeared that they
> alway model navigable associations by using the alternative UML
> representation where navigable ends are owned by the Association, instead of
> owned by the source class (as indicated by Kenn). Both are valid UML
> representations, but for code generation from the model I think that tools
> should use the Class owned navigable ends by default. This is a key reason
> why I chose not to look at TopCased beyond my initial review...
>
> Regards,
> Dave Carlson
>
> "Kenn Hussey" <khussey@ca.ibm.com> wrote in message
> news:f8lemd$70k$1@build.eclipse.org...
>> Toshinao,
>>
>> Both of the association ends are owned by the association, which means
>> that when the model is mapped to EMOF (Ecore), the properties will be
>> lost. In order to preserve an association end, the property representing
>> it needs to be owned by the end type (i.e. the class).
>>
>> Kenn
>>
>> "Toshinao Ishii" <i_j_e_x_a@yahoo.co.jp> wrote in message
>> news:f8lckb$lj6$1@build.eclipse.org...
>>> Hi.
>>>
>>> I have just started writing a simple UML model
>>> (by using TOPCASED TOOLS) and convert it to
>>> ecore. A problem I met is that a UML element
>>> of Association is not converted to an EMF element
>>> but it just disappears.

Both of the association ends are owned by the association, which means that
when the model is mapped to EMOF (Ecore), the properties will be lost. In
order to preserve an association end, the property representing it needs to
be owned by the end type (i.e. the class).

Toshinao,
I took a quick look at TopCased a few months ago, and it appeared that they
alway model navigable associations by using the alternative UML
representation where navigable ends are owned by the Association, instead of
owned by the source class (as indicated by Kenn). Both are valid UML
representations, but for code generation from the model I think that tools
should use the Class owned navigable ends by default. This is a key reason
why I chose not to look at TopCased beyond my initial review...

Regards,
Dave Carlson

"Kenn Hussey" <khussey@ca.ibm.com> wrote in message
news:f8lemd$70k$1@build.eclipse.org...
> Toshinao,
>
> Both of the association ends are owned by the association, which means
> that when the model is mapped to EMOF (Ecore), the properties will be
> lost. In order to preserve an association end, the property representing
> it needs to be owned by the end type (i.e. the class).
>
> Kenn
>
> "Toshinao Ishii" <i_j_e_x_a@yahoo.co.jp> wrote in message
> news:f8lckb$lj6$1@build.eclipse.org...
>> Hi.
>>
>> I have just started writing a simple UML model
>> (by using TOPCASED TOOLS) and convert it to
>> ecore. A problem I met is that a UML element
>> of Association is not converted to an EMF element
>> but it just disappears.

Dave Carlson wrote:
> Toshinao,
> I took a quick look at TopCased a few months ago, and it appeared that they
> alway model navigable associations by using the alternative UML
> representation where navigable ends are owned by the Association, instead of
> owned by the source class (as indicated by Kenn). Both are valid UML
> representations, but for code generation from the model I think that tools
> should use the Class owned navigable ends by default. This is a key reason
> why I chose not to look at TopCased beyond my initial review...
>
> Regards,
> Dave Carlson
>
> "Kenn Hussey" <khussey@ca.ibm.com> wrote in message
> news:f8lemd$70k$1@build.eclipse.org...
>> Toshinao,
>>
>> Both of the association ends are owned by the association, which means
>> that when the model is mapped to EMOF (Ecore), the properties will be
>> lost. In order to preserve an association end, the property representing
>> it needs to be owned by the end type (i.e. the class).
>>
>> Kenn
>>
>> "Toshinao Ishii" <i_j_e_x_a@yahoo.co.jp> wrote in message
>> news:f8lckb$lj6$1@build.eclipse.org...
>>> Hi.
>>>
>>> I have just started writing a simple UML model
>>> (by using TOPCASED TOOLS) and convert it to
>>> ecore. A problem I met is that a UML element
>>> of Association is not converted to an EMF element
>>> but it just disappears.