| Summary: | Cannot validate EClass stereotype | ||
|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Ed Willink <ed> |
| Component: | Core | Assignee: | UML2 Inbox <mdt-uml2-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | Kenn.Hussey, nicolas.f.rouquette |
| Version: | 3.1.0 | Flags: | Kenn.Hussey:
indigo+
|
| Target Milestone: | SR1 | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 287010 | ||
|
Description
Ed Willink
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. See http://www.omg.org/issues/issue13482.txt for some background on (one incarnation of) this issue at the OMG. 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 The fix is available in builds at http://www.eclipse.org/modeling/mdt/downloads/?showAll=1&hlbuild=I201008301532&project=uml2#I201008301532 (3.2.0) and http://www.eclipse.org/modeling/mdt/downloads/?showAll=1&hlbuild=M201008301351&project=uml2#M201008301351 (3.1.1). Closing for Indigo release. |