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 116797 - A method argument need to be saved twice if argument has the same name as a method
Summary: A method argument need to be saved twice if argument has the same name as a m...
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Class (show other bugs)
Version: 5.x
Hardware: All Linux
: P3 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on: 149000
Blocks:
  Show dependency tree
 
Reported: 2007-09-26 10:18 UTC by quetzal
Modified: 2009-05-25 21:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 quetzal 2007-09-26 10:19:03 UTC 
Create a Class Diagram and create a class on it. Than add a method called "test" with an argument called "test" of type
String(should be: "test(test:String)") and hit the Enter key. You'll should see a new method test(Unknown:String). You
have to correct "Unknown" to "test" again to get test(test:String).
Comment 1 Joanne Lau 2008-06-10 22:43:36 UTC 
Still exists in 6.5
Comment 2 Thuy.d Nguyen 2008-10-02 19:30:05 UTC 
This issues is seen on both UML Platform-Independent Model and Java-Platform Model.
Comment 3 Thuy.d Nguyen 2008-10-03 22:38:27 UTC 
The root cause of this issue is the "value" field of the propertyElement representing a parameter name was populated
with the operation name instead of the previous name of the parameter; therefore, in the case the new parameter had the
same name as the operation, the new name could never be set, because of the following check:
if (propertyElement.getValue() != newName)
{
   // set the new name
}

Fixed to correctly populate the propertyElement with the previous name of the parameter.
changeset 2f3ddccc78ee in uml-main
details: http://hg.netbeans.org/uml-main?cmd=changeset;node=2f3ddccc78ee
Comment 4 Trey Spiva 2008-10-06 18:05:00 UTC 
Reviewed
Comment 5 Trey Spiva 2008-10-10 17:05:17 UTC 
The fix for this issue causes a regression.  The regression is issue 149577.  Therefore I am having to reopen this issue.  Also since there is a work around I am 
lowering the priority.