|Re: UML 2 ecore and association.navigableOwnedEnd [message #818974 is a reply to message #818955]
||Mon, 12 March 2012 10:29
| Ed Willink
Registered: July 2009
I agree that it is surprising, but it is also reasonable.
When the ends are association-owned, the relevant classes have no
corresponding properties, so to create such 'properties' in Ecore (or
EMOF) would be differently surprising.
EMOF/Ecore is not UML and Associations are one of the most fundamental
differences between them.
There are many processing options for the UML2Ecore converter; it is
possible that one of them can be used to influence the above behaviour.
On 12/03/2012 10:11, Fabien Giquel wrote:
> I am using uml to ecore converter for initializing some EMF project
> from one uml model. If i create some uml model with two classes and
> one bidirectional association between them, i see that :
> - if uml properties (roles) are owned by the uml classes, the ecore
> will define references between classes. That's fine.
> - however if uml properties are owned by the uml association in
> indicating them as "navigableOwnedEnd" on the association, the ecore
> will not define references between the two classes.
> Is this second behavior known and wished for uml2ecore conversion ? Or
> is that some uml2ecore issue ?
> Thanks un advance,
Powered by FUDForum
. Page generated in 0.05519 seconds