search

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

[pivot] Support direct UML to Piviot loading #815

Open eclipse-ocl-bot opened 2 months ago

eclipse-ocl-bot commented 2 months ago

| --- | --- | | Bugzilla Link | 365447 | | Status | NEW | | Importance | P3 normal | | Reported | Dec 02, 2011 10:16 EDT | | Modified | Aug 28, 2023 03:23 EDT | | Version | 4.0.0 | | Depends on | 581543 | | Reporter | Ed Willink |

Description

UMML loading for the pivot current used a UML2Ecore conversion to allow reuse of the Ecore2Pivot loader. This loses UML Association, Profile and merge details.

Complete development of the direct UML2Pivot loader.

eclipse-ocl-bot commented 2 months ago

By Ed Willink on Jun 27, 2012 06:32

UML2Pivot (on bug/365447) supports loading of Association ends and Profiles enabling the elimination of UML2Ecore2Pivot for all JUnit tests (excpt those that explicitly test an Ecore intermediate). The loader successfully loads the UML 2.5 XMI, which after trivial fixes loads error free.

The UML coverage is currently pragmatic, so a detailed review is required.

There is no support for Package merge; probably adequaltely handled by MDT/UML2 during 'load'.

There is no support for Association classes; probably need to create them even though ends are migrated to classes.

Need Pivot2UML to support full round-trip testing.

eclipse-ocl-bot commented 2 months ago

By Ed Willink on Aug 30, 2012 13:12

Support for Stereotypes has been added.

eclipse-ocl-bot commented 2 months ago

By Ed Willink on Aug 28, 2023 03:23

The Bug 581543 rationalization to combine OCLstdlib and Pivot and Tables/Metamodel merits a revisit of the UML loading which suffers from the considerable complexity of unifying Eclipse UML2 and OMG UML metamodels. As a minimum this burns loading time. It has potentially evolved so that in test_tutorial_umlValidation_436903 we seem to need to load Pivot from Ecore so that UML can be.

Now that Eclipse UML2 is VERY stable, it would be much better to load a single Pivot UML metamodel that was auto-generated at compile-time. The relevant auto-generation should be accessible for those occasions when a user really wants a custom UML.