-
Key: MOF26-41
-
Status: open Implementation work Blocked
-
Source: oose Innovative Informatik eG ( Mr. Axel Scheithauer)
-
Summary:
MOF merges the UML package into its Reflection package. The UML contains many packages, such as CommonStructure. The package merge defines that such packages are deep copied into the resulting package. All the packages of the UML are also imported into the UML package. Package merge just copies these import relationships. It doesn't merge the imported elements: UML 2.5: Imported elements are not merged (unless there is also a PackageMerge to the Package owning the imported element).
In effect, it means that MOF contains two unrelated element definitions: CommonStructure::Element and Reflection::Element. In fact all MOF elements are not merged with their UML counterparts.
In UML 2.4 all the packages were merged into the UML package. Therefore, all elements were directly contained in this package. Therefore, it was sufficient to merge it.
A possible solution: Create in MOF a package structure mirroring the UML packages.
-
Reported: MOF 2.5.1 — Fri, 7 Oct 2022 12:10 GMT
-
Updated: Thu, 27 Oct 2022 16:53 GMT
MOF26 — merging the UML package does not merge the elements of UML
- Key: MOF26-41
- OMG Task Force: MOF 2.6 Family RTF