Community
Participate
Working Groups
UML2 Superstructure 2.1 says: "An end property of an association that is owned by an end class or that is a navigable owned end of the association indicates that the association is navigable from the opposite ends, otherwise the association is not navigable from the opposite ends." It would be nice if the UML2EcoreConverter would support tranformation of properties that are specified using the second of the above mentioned options also.
Bug #157976 should first be resolved, as this would allow for an easier implementation here.
Only ends that are owned by end types are mapped to Ecore references; if, at some point in the future, EMF provides support for the concept of "associations", conversion of ends owned by associations could be revisited.
Bug #157976 has already been fixed for awhile so has this been fixed too?
Does Bug #105920 still needs to be resolved before this one can be fixed?
Yes, EMF would need to provide support for modeling associations (as per comment #2).
*** Bug 213894 has been marked as a duplicate of this bug. ***
Support for conversion of owned (by the association) member ends, if/when provided, will ignore navigability since association ends are always navigable (and always have a multiplicity of 1) from the perspective of their instances (links).
Created attachment 86883 [details] UML patterns Here is a model containing the UML structures that would map to the corresponding structures in the Ecore model Ed attached to bug 105920. Note that associations can be substituted for association classes in all cases except for 'zeroOwnedEnds' (since, in the absence of owned attributes, no value would be added).
Don't forget to update the Ecore profile so that the EClass stereotype can be applied to associations.