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 78829 - class stereotype is missed after transformation to interface
Summary: class stereotype is missed after transformation to interface
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Class (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-21 23:32 UTC by bugbridge
Modified: 2007-02-08 14:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2006-06-21 23:32:01 UTC 
Original status: 1-Dispatched; Suggested Status: NEW

Original submitter: akorostelev

Description:
how to reproduce:
- create uml project 
- create class diagram.
- put boundary class to diagram
new class with stereotype <<boundary>> is created.
- transform it to Interface.
- transform back to class.
stereotype <<boundary>> is missed.

After transforming to any other type stereotype is not missed.
Comment 1 Trey Spiva 2006-08-01 22:15:24 UTC 
This is by design.  It is no longer a boundry class, it is a class.  When you
transform to an interface the stereotype is removed.
Comment 2 Alexandr Scherbatiy 2006-11-14 11:10:39 UTC 
The behaviour is inconsistent. 
Transform the boundary class to enumeration.
The stereotype is not removed.
What is the difference between boundary class transformation
to interface and to enumeration?
Comment 3 Trey Spiva 2007-02-07 20:26:54 UTC 
When transforming to an interface, all existing stereotypes where being removed.  That is no longer the 
case.  The  "interface" stereotype is now added to the list of existing stereotypes.
Comment 4 Alexandr Scherbatiy 2007-02-08 14:44:01 UTC 
verified