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 119937 - RE Operation: variable name becomes representing classifier
Summary: RE Operation: variable name becomes representing classifier
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Reverse Engineering (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Viktor Lapitski
URL:
Keywords: REGRESSION
: 98975 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-10-24 17:14 UTC by Peter Lam
Modified: 2007-10-31 00:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
incorrect lifeline (22.07 KB, image/png)
2007-10-24 17:14 UTC, Peter Lam 		Details
correct sequence diagram for issue 119937 (80.95 KB, image/png)
2007-10-26 18:10 UTC, Peter Lam 		Details
correct sequence diagram for issue 98975 (76.59 KB, image/png)
2007-10-26 18:10 UTC, Peter Lam 		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 Peter Lam 2007-10-24 17:14:01 UTC 
The is a regression.

Reverse engineer the following operation. The "length" variable is displayed as representing classifier for the lifeline
where it should be "length : int". See attached screenshot.

 public void testConditionIf2(){
        Method[] method = getClass().getMethods();
        if ( method != null && method.length > 0){
            System.out.println(method[0].getName());
        }else{
            System.out.println(getClass().getName());
        }
    }
Comment 1 Peter Lam 2007-10-24 17:14:34 UTC 
Created attachment 51600 [details]
incorrect lifeline
Comment 2 Viktor Lapitski 2007-10-26 02:30:32 UTC 
just checked with 5.5 - it behaves the same, so removed the regression keyword
Comment 3 Peter Lam 2007-10-26 18:09:05 UTC 
The reason I marked it as a regression is that this issue has been fixed and I just found the issue number and that is
issue 98975 after you confirmed it's the same as in NB5.5. And now issue 98975 is failing too with similar source. See
attached screenshot using build 200709180323 that has the fix and showing correct sequence diagrams for both this case
and the case in issue 98975. Marking it as regression again since it's a recent regression to the previous fix.
Comment 4 Peter Lam 2007-10-26 18:10:03 UTC 
Created attachment 51803 [details]
correct sequence diagram for issue 119937
Comment 5 Peter Lam 2007-10-26 18:10:35 UTC 
Created attachment 51804 [details]
correct sequence diagram for issue 98975
Comment 6 Peter Lam 2007-10-26 18:12:13 UTC 
*** Issue 98975 has been marked as a duplicate of this issue. ***
Comment 7 Viktor Lapitski 2007-10-29 08:51:40 UTC 
fixed.
Comment 8 Peter Lam 2007-10-31 00:29:33 UTC 
verified in trunk build 20071030.