Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 321461

Summary: Cannot validate EClass stereotype
Product: [Modeling] MDT.UML2 Reporter: Ed Willink <ed>
Component: CoreAssignee: UML2 Inbox <mdt-uml2-inbox>
Status: CLOSED FIXED QA Contact:
Severity: major    
Priority: P3 CC: Kenn.Hussey, nicolas.f.rouquette
Version: 3.1.0Flags: Kenn.Hussey: indigo+
Target Milestone: SR1   
Hardware: PC   
OS: Windows Vista   
Whiteboard:
Bug Depends on:    
Bug Blocks: 287010    

Description Ed Willink CLA 2010-08-01 11:02:38 EDT
Symptom 1. MDT/OCL UML models have many hundreds of validation errors in Helios; Bug 287010.

Symptom 2. Adding a generalisation to a sterotyped class, saving and reloading loses the addition.

Simple repro.

Create a UML model with a single Class. Apply the EClass sterotype. Validate.
Shows three errors such as

The required feature 'base_Interface' of 'EClass ...' must be set

I cannot see anyway to set this feature.

It would appear that enhanced Ecore validation in Helios has revealed a latent bug in the Ecore profile.
Comment 1 Kenn Hussey CLA 2010-08-19 14:59:19 EDT
The issue with not being able to validate the EClass stereotype has been around for some time. We submitted the issue to the OMG several years ago, hoping for a quick turnaround. I suppose at this point it's safe to assume it won't be address anytime soon.

I've committed a "fix" for the Ecore profile, to both the HEAD and R3_1_maintenance streams.
Comment 2 Kenn Hussey CLA 2010-08-19 15:41:50 EDT
See http://www.omg.org/issues/issue13482.txt for some background on (one incarnation of) this issue at the OMG.
Comment 3 Nicolas Rouquette CLA 2010-08-19 16:34:20 EDT
There's a definite need for clarifying the semantics of stereotypes, particularly that of instances of stereotypes. Although several profile/stereotype related problems have been fixed in UML 2.3, the question of clarifying what a stereotype instance really hasn't. The MOF-equivalent construction is an incomplete answer. The underlying problem is not a trivial matter because, fundamentally, profiles & stereotypes straddle the boundary between two modeling levels: i.e., the metamodel (e.g., OMG or Eclipse' definition of the UML metamodel) and models (e.g., Joe's UML model). For more on this topic, see:

http://www.omg.org/issues/uml2-rtf.open.html#Issue15001
Comment 5 Kenn Hussey CLA 2011-05-31 10:36:43 EDT
Closing for Indigo release.