Bugzilla – Full Text Bug Listing
| Summary: | UML editor only shows type of stereotype attributes, not qualified name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Volker Stolz <stolz+bugzilla> | ||||
| Component: | Core | Assignee: | Kenn Hussey <Kenn.Hussey> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P2 | Keywords: | plan | ||||
| Version: | 2.2.0 | Flags: | Kenn.Hussey:
kepler+
|
||||
| Target Milestone: | M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| URL: | http://rcos.iist.unu.edu | ||||||
| Whiteboard: | Community Support | ||||||
| Attachments: |
|
||||||
The attached picture suggests that something is wrong with your environment, because at the very least I would expect to see things like "{Protocol} -> Protocol_CD" and "{Protocol} -> P2" in the list.
In any case, I have added a qualified text provider for stereotype applications, so now you'll see things like "{rCOS::Protocol} -> CoCoME::CoCoME_ComponentModel::Protocol_CD - CoCoME.uml" and "{rCOS::Protocol} -> CoCoME::CoCoME_ComponentModel::P2 - CoCoME.uml" in the list.
The changes have been committed/pushed to the 'master' branch in git.
The changes are available in the UML2 4.1 M7 build (for Kepler). |
Created attachment 115217 [details] Screen shot Build ID: I20080617-2000 Steps To Reproduce: 1. create profile with a stereotype (S) for e.g. a package. Make this stereotype have an attribute (S.a) of another stereotype (or it's own type). 2. create a model referencing the above profile, containing two packages which has the above stereotype applied. 3. Try setting the stereotype attribute value S.a of one of the two packages in the UML editor -- the list view only shows the type S, so you cannot distinguish the elements (packages P2 and Control_CD in the screen shot) you're selecting from. More information: I know that in general a qualified name might not be available to display here, but there must be some way of giving more helpful information on screen. Or is there anything I can do to improve the profile so that Eclipse's logic of deciding whether a qualified name is available works better?