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.
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).
Still exists in 6.5
This issues is seen on both UML Platform-Independent Model and Java-Platform Model.
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
Reviewed
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.