Bug 163808 - Support OCL Expressions on UML Metamodel
Summary: Support OCL Expressions on UML Metamodel
Status: CLOSED FIXED
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Linux
: P1 enhancement (vote)
Target Milestone: M5   Edit
Assignee: Christian Damus CLA
QA Contact:
URL:
Whiteboard:
Keywords: api, plan
Depends on:
Blocks:
 
Reported: 2006-11-08 09:26 EST by Christian Damus CLA
Modified: 2011-05-27 02:41 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Damus CLA 2006-11-08 09:26:04 EST 
Implement a UML environment for OCL, as a complement to the current Ecore environment.  This will enable OCL constraints and queries on instances of the UML metamodel.

A secondary goal would be to clean up the Ecore environment to remove the malapropos UML-isms.
Comment 1 Christian Damus CLA 2006-11-17 11:58:06 EST 
Est.: 3w
Comment 2 Christian Damus CLA 2007-01-26 16:51:53 EST 
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).
Comment 3 Nick Boldt CLA 2008-01-28 16:36:45 EST 
Move to verified as per bug 206558.
Comment 4 Ed Willink CLA 2011-05-27 02:39:23 EDT 
Closing after over a year in verified state.
Comment 5 Ed Willink CLA 2011-05-27 02:41:27 EDT 
Closing after over a year in verified state.