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.
This is an intermittant problem that can not be reproduce consistently. It only happens sometimes. So, there must be a problem somewhere that should be looked into. Repro steps: - create a java-platform uml project - create a collaboration diagram using the default diagram name - add and name a few elements on the diagram - click on the "x" from the diagram tab to close the diagram - select Save from the dialog to save the diagram before closing - expand the collaboration diagram interaction node Result: the collaboration diagram node is missing - expanding the Diagrams node now will pop up a dialog indicating "" is not a valid diagram name.
netcat user also experienced the issue with component diagram.
See issue 123909.
*** Issue 123909 has been marked as a duplicate of this issue. ***
Fine-tuned the code to make sure the name, displayname and itemText fileds of a diagram node are properly set when the diagram node is created and renamed.
verified in trunk build 20080117
while testing 6.1 m1 build 200801222102, I created a number of different diagrams with the use case diagram created last from the list. After adding some elements and saved the use case diagram, I closed the use diagram but could not open it even though the diagram node/name is still under the Model node. Then expanding the Diagrams node popped up the following informational dialog. "" is not a valid diagram name. Attached is the project that will should this dialog if it's opened and the Diagrams node get expanded. It does take a while to expand too.
Created attachment 55460 [details] sample model project
Created attachment 55461 [details] ide log file
The attached sample uml project shows that the usecase diagram was not being saved properly when it was closed. The etlp file of the usecase diagram has no content in it which causes the reported behavior when the diagram is opened. I'm looking into the root cause of this issue.
Modified the save logic to write diagram data to *.etlp and *.etld files directly eliminating the temp files. I also used FileObject and FileObject.getInputStream() in the file-saving process.
Verified in nb6.1 build 200802191203. Tried many times with the same scenario but no longer reproducible. Will reopen if problem exists again in the future.