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.
Summary: | Addition of parameter to realized interface method is not handled for class | ||
---|---|---|---|
Product: | uml | Reporter: | bugbridge <bugbridge> |
Component: | Synchronization | Assignee: | _ jyothivasa <jyothivasa> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | sj-nb |
Priority: | P2 | Keywords: | REGRESSION |
Version: | 5.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
bugbridge
2006-07-25 16:42:18 UTC
OK, I understand now and am able to reproduce. The default is good as is (Ask to redefine) as that was the default in Buzz. If we default to redefine all instances without asking, the user may not know they can be prompted and might not like that they were not asked at least the first time. -- Migrating Comment From Internal Bug Tracking System As per Trey, we need to call JavaMethodChangeFacility.parameterAdded/Change, but this is not producing consistently correct results. I am able to add params and it works, but no dialog prompting. However, changing or deleting a parameter, or insterting one in between the other existing parameters is very problematic. This fix may require much more work than first thought. -- Migrating Comment From Internal Bug Tracking System This issue is beyond just adding a parameter to the interface's src. Known issues include: 1. adding an operation 2. changing the return type of the oper 3. changing the name of the oper 4. deleting an operation 5. adding a new parameter 6. changing the number of parameters 7. changing the type of the parameter, etc doesn't get propagated. Fixed the issue in the bug description, as well as all of the 7 listed issues. verified all listed cases in coke build 17. *** Issue 78515 has been marked as a duplicate of this issue. *** *** Issue 78534 has been marked as a duplicate of this issue. *** |