This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 137859 - Wrong stereotype value for pkg after removing stereotype
Summary: Wrong stereotype value for pkg after removing stereotype
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: Properties (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-20 23:08 UTC by Joanne Lau
Modified: 2009-05-25 21:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screeshot after removing tagged value (29.04 KB, image/png)
2008-06-20 23:09 UTC, Joanne Lau
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joanne Lau 2008-06-20 23:08:07 UTC
Build: 080619

- DnD a package (pkg2) to the class diagram
- In the property window, click "..." of the tagged values field
- Click add to add a tagged value 
  (enter e.g. Name=tt, Alias=tt, Value=3) and click OK
- Save all
- Click the tagged value field in the property window again
  This time select it, and click Remove,  click OK
- Click the tagged value field again,
  the name of the tagged property value has changed to the pkg name
  Select and remove it
- Repeat previous step again,  the value is still there 
  Can't get rid of the tagged value
Comment 1 Joanne Lau 2008-06-20 23:09:19 UTC
Created attachment 63189 [details]
screeshot after removing tagged value
Comment 2 Joanne Lau 2008-07-01 19:17:00 UTC
This issue applies to activity diagram as well when adding/removing stereotype in partition
Comment 3 Joanne Lau 2008-07-01 19:34:59 UTC
With the latest build 080701, I couldn't reproduce the issue with adding/removing tagged value in the pkg, however
adding/removing stereotype in pkg still exists.  
Comment 4 Trey Spiva 2008-07-11 14:52:34 UTC
This is a problem in the property editor that has been around for a while.
Comment 5 Trey Spiva 2008-07-31 17:41:33 UTC
The issue only occurs when the user opens the custom property editor, moves the stereotype, closes the editor, and opens it again.  If the user first goes to 
another model element, so the set of properties editor show a new set of properties, then comes back to the original node this problem will not change.  
Comment 6 Trey Spiva 2008-07-31 18:07:11 UTC
Since this issue is a low use case, and the data is not corrupted I am going to lower this issue.