| Summary: | Support OCL Expressions on UML Metamodel | ||
|---|---|---|---|
| Product: | [Modeling] OCL | Reporter: | Christian Damus <give.a.damus> |
| Component: | Core | Assignee: | Christian Damus <give.a.damus> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P1 | Keywords: | api, plan |
| Version: | 1.0.1 | ||
| Target Milestone: | M5 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Christian Damus
Est.: 3w Committed the feature to OCL's new CVS home in the Modeling project:
/cvsroot/modeling/org.eclipse.mdt/org.eclipse.ocl
This delivery introduces the org.eclipse.ocl.uml plug-in providing a UML binding (environment implementation) for the OCL parser. It supports, in addition to what the Ecore binding offers, the following UML-specific capabilities:
- navigation through static properties
- calling static operations
- state expressions
- association class navigation
- qualified association and association-class navigation
- signals in message expressions
OCL expressions parsed in the context of a classifier in a UML metamodel can be evaluated on:
- InstanceSpecifications, with limitations vis-a-vis operation calls. Association-class and
qualified association navigation are supported
- EObjects (instances of EClasses statically generated from UML models or dynamically
created by UMLUtil), with limitations vis-a-vis association class navigation and qualified
association navigation
Constraints on Stereotypes are supported. Evaluation of such constraints on elements of a UML model that have the stereotype applied are implicitly evaluated on the stereotype application (instance).
Move to verified as per bug 206558. Closing after over a year in verified state. Closing after over a year in verified state. |