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 123909 - "" is not a valid diagram name
Summary: "" is not a valid diagram name
Status: VERIFIED DUPLICATE of bug 122924
Alias: None
Product: uml
Classification: Unclassified
Component: General Diagram (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Thuy.d Nguyen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-12 20:58 UTC by George Vasick
Modified: 2008-02-22 08:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
model explorer showing diagram node with missing name. (35.51 KB, image/png)
2007-12-12 21:05 UTC, George Vasick
Details
error popup (14.17 KB, image/png)
2007-12-12 21:06 UTC, George Vasick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description George Vasick 2007-12-12 20:58:30 UTC
Steps to reproduce:

0) start in a fresh userdir
1) reverse engineer UML core, source only, deselect the test package.
2) expand model -> org -> netbeans -> modules -> uml -> core -> reverseengineering -> reframework.
3) multiple select all members of the reframework package, parsingframework package through REXMLCollection class.
4) CDFS to a class diagram.  use the default diagram name.
5) click the X on the diagram tab to close the diagram.
6) notice the diagram name is missing (see capture5).
7) attempt to expand the diagrams under the uml project.
8) notice error popup: "" is not a valid diagram name
Comment 1 George Vasick 2007-12-12 21:04:01 UTC
See also issue 122924.
Comment 2 George Vasick 2007-12-12 21:05:23 UTC
Created attachment 54209 [details]
model explorer showing diagram node with missing name.
Comment 3 George Vasick 2007-12-12 21:06:01 UTC
Created attachment 54210 [details]
error popup
Comment 4 Peter Lam 2007-12-13 17:52:07 UTC
Looks like this problem exists in an inconsistent scenario. I tried similar steps for different projects than the UML
core, but could never reproduce the issue with class diagram. Same thing with the collaboration diagram in issue 122924
which the problem is not reproducible consistently. But I believe there's a common issue when clicking on the X of the
diagram tab to close the diagram that something is not done properly in some cases.
Comment 5 George Vasick 2008-01-04 17:16:07 UTC
Can no longer reproduce consistently.
Comment 6 George Vasick 2008-01-11 21:38:38 UTC

*** This issue has been marked as a duplicate of 122924 ***
Comment 7 Peter Lam 2008-02-22 08:27:02 UTC
verified in latest nb 6.1 build 200802191203. Tried a few times but no longer reproducible with the same scenario using
the uml core source.