Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 252876 - [ProfileDefD] OCL Constraint element
Summary: [ProfileDefD] OCL Constraint element
Status: RESOLVED FIXED
Alias: None
Product: GMF-Tooling
Classification: Modeling
Component: Samples (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tatiana Fesenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 199739
  Show dependency tree
 
Reported: 2008-10-30 15:21 EDT by Tatiana Fesenko CLA
Modified: 2012-12-11 15:13 EST (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 Tatiana Fesenko CLA 2008-10-30 15:21:12 EDT 
OCL Constraint is a Contraint, which OpaqueExpression has 'ocl' language. OCL constraint is probably the most-They are widespread kind of a constraint. 
Now, to create OCL constraint the user has to create 'Constraint' element using UML2 Tools, then go to UML Editor and edit 'language' property of OpaqueExpression there. Then the user returns to UML2 Tools editors and works with the constraint.
The possible solutions are
1) Create OCL Constraint palette entry
2) Allow to edit properties of nested OpaqueExpression in the properties view. E.g. when select a constraint - properties of the constraint are displayed, if select the label - then properties of OpaqueExpression will be available in the PropertiesView. Or show properties of nested elements in tree-like structure in the properties view.
Comment 1 Tatiana Fesenko CLA 2009-01-13 10:44:35 EST 
2) Allow to edit properties of nested OpaqueExpression in the properties view. --fixed
Comment 2 Tatiana Fesenko CLA 2009-01-13 11:22:43 EST 
Fixed