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 114936 - Navigable association still showing in projects window after removed from the diagram editor
Summary: Navigable association still showing in projects window after removed from the...
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Class (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: Viktor Lapitski
URL:
Keywords: REGRESSION
Depends on:
Blocks: 110808
  Show dependency tree
 
Reported: 2007-09-06 19:23 UTC by Joanne Lau
Modified: 2007-10-17 19:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
screenshot attached (70.59 KB, application/octet-stream)
2007-09-06 19:23 UTC, Joanne Lau 		Details
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 Joanne Lau 2007-09-06 19:23:11 UTC 
Beta1 200709060000

Steps to repro:
1) Create a class diagram, drop 4 class elements (c1, c2, c3, c4) to the diagram editor
2) Select Navigable Association element from the palette and connect it from:
        c1 -> c3
        c3 -> c4 
        c4 -> c2
3) From the projects window, expand Model -> c4 -> Relationships -> Associations
   Notice 3 associations created as expected
4) From the diagram editor, add another association to c4 -> c1
5) From the projects window, expand Model -> c4 -> Relationships -> Associations
   Notice 4 associations created as expected
6) From the diagram editor, Right click assocation from c4 -> c1, click <Delete>
   Select checkbox for permanent deletion from project, seeing that the association is deleted
7) From the projects window, Association still showing in the projects window

   Close and reopen the project, the issue is still there.
   (See attached screenshot)
Comment 1 Joanne Lau 2007-09-06 19:23:33 UTC 
Created attachment 48318 [details]
screenshot attached
Comment 2 Yang Su 2007-09-06 23:16:56 UTC 
I cannot reproduce this issue in trunk 9/6/07.

In your step #3, there should be only two associations under c4, you mentioned three, what are those three?
Again, in #5, I see only three, you mentioned four. Something was not right before c4 -> c1 association was deleted, how
did you get into this situation at step 3?
Comment 3 Joanne Lau 2007-09-07 00:01:50 UTC 
Clarification on the steps:
  3)  2 association links are expected
  5)  3 association links are expected after adding connection c4->c1

The issue is reproducible in today's NB 6.0 Beta1 build
Comment 4 Yang Su 2007-09-07 00:38:27 UTC 
OK, I see, I'm not sure it's a regression, it's just another symptom of model tree refresh issue. In step 5, you need to
fully expand all association nodes under c4 to reproduce.

Workaround:  right click model node to bring up filter dialog, click 'OK'. Now expand nodes to get the refreshed view.

Perhaps, we should reconsider 'Refresh' menu now? No one would know default 'Filter' action does the trick.
Comment 5 Thuy.d Nguyen 2007-09-14 01:11:05 UTC 
This issue has also been addressed by the fix for issue 110809.  Please verify.  
(Tip for easier testing: you can label/name the links as, say,  1-3, 3-4...,  to know which is which when you delete or
add a link.)
Comment 6 Joanne Lau 2007-09-18 18:05:26 UTC 
The issue is still reproducible with current build 200709180324 using the same scenario. The links in this case
are unlabeled.  However the issue is not reproducible when the links are labeled.
Comment 7 Peter Lam 2007-10-01 18:05:53 UTC 
Just verified that this is a regression from nb5.5. 
This problem still exists in today's instrumented build 2007100100405.
Comment 8 Thuy.d Nguyen 2007-10-06 01:20:42 UTC 
This issue and issue 116029 have the same root cause (certain nodes can not be deleted from the tree). The regression is
due to a recent change to the underlined implementation of node collection in an effort to fix performance issue seen on
the project tree.  Reassigning to lvv for further investigation.
Comment 9 Viktor Lapitski 2007-10-12 07:33:56 UTC 
fixed.
Comment 10 Joanne Lau 2007-10-17 19:05:49 UTC 
Fix verified in Beta 2 build