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 104173 - Classifier name is set to 'Unnamed' after change to wrong value
Summary: Classifier name is set to 'Unnamed' after change to wrong value
Status: REOPENED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Sequence (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-17 14:32 UTC by Sergey Petrov
Modified: 2009-05-25 21:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Petrov 2007-05-17 14:32:07 UTC
reproducible with 070515

Classifier name is set to 'Unnamed' in lifeline on diagram after change to wrong
value (but remains correct in properties)

steps:
1. create sequence diagram
2. add lifeline
3. specify 'BUBUBU' as lifeline name
4. with diagram editor try to change  'BUBUBU' to '.BUBUBU'
5. say yes to create new classifier
dialog with info about wrong classifier name appears
6. close the dialog
Classifier name is set to 'unnamed' on diagram
workaround/restore value:
7. go to 'representing Classifier' property of lifeline (just click in value)
8. select the lifeline on the diagram
classifier name is restored

there is also side effect: after each unsuccessful change new 'unnamed' class
appears in model, may be I'll file it as a separate issue later
Comment 1 George Vasick 2007-05-17 18:47:50 UTC
Planned for drawing area upgrade after NB 6.0.
Comment 2 George Vasick 2007-05-18 00:41:46 UTC
Should not use resolved/later status.
Comment 3 George Vasick 2007-06-28 22:52:20 UTC
Targeted in drawing area redesign.
Comment 4 George Vasick 2007-07-04 00:56:41 UTC
Restoring original priority and using the standard NB waiver process.
Comment 5 George Vasick 2008-01-02 17:49:18 UTC
Diagram area bugs waived for 6.0 will also be waived for 6.1.
Comment 6 Peter Lam 2008-06-17 06:43:42 UTC
still exists in 6.5