| Summary: | Add new methods on Element to handle multi-valued stereotype attribute | ||
|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Alessandro Romero <romgerale> |
| Component: | Core | Assignee: | UML2 Inbox <mdt-uml2-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | Kenn.Hussey |
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Alessandro Romero
I hesitate to add such a method, since the current getValue(...) method essentially mimics the analog in EMF, eGet(...). Does this same problem exist when doing something similar for Ecore models? Is there no way to "cast" the result of getValue(...) so that the right type is expected? Sorry, I have been so focused on my problem and how to resolve based on messages and mailing list, such as: http://dev.eclipse.org/newslists/news.eclipse.modeling.m2m/msg04703.html That I stopped to try cast elements (so simple). modeltype OCL uses ocl('http://www.eclipse.org/ocl/1.1.0/oclstdlib.ecore'); x := class.getValue(stereotype,"feature").oclAsType(EEList).asSequence(); x+= b.oclAsType(oclstdlib::T); Work very well! Please ignore this enhancement! OK, resolving this as "won't fix". Closing for Indigo release. |