Bug 452676 - [ProfileDiagram][OCL] Should warn user when defining profile having unnamed OCL constraints
Summary: [ProfileDiagram][OCL] Should warn user when defining profile having unnamed O...
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: SR2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: dx deploy normal
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-21 11:21 EST by Christian Damus CLA
Modified: 2017-09-08 09:50 EDT (History)
3 users (show)

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 2014-11-21 11:21:40 EST 
As noted in bug 452621, if an OCL constraint in a profile has no name, then the profile definition transformation ignores it and it (rightly so) doesn't end up in the Ecore definition and therefore does not participate in model validation.

Steps to reproduce:

1. Create a UML profile with some OCL constraint on a stereotype extending some
   metaclass.
2. Do not give the constraint a name.  If it has one by default, delete it.
3. Apply the profile to a model and the stereotype to some element that should
   violate the constraint.
4. Validate the model and see no problem reported for the constraint on the
   stereotyped element.
Comment 1 Remi Schnekenburger CLA 2014-12-12 03:02:53 EST 
A new constraint should be implemented in Papyrus. It would warn users when designing and defining profiles.