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: | Refactoring JSR-296 @Action method doesn't work | ||
|---|---|---|---|
| Product: | guibuilder | Reporter: | mrmorris <mrmorris> |
| Component: | App Framework | Assignee: | issues@guibuilder <issues> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
IMO this should be handled by separate refactoring plugin We should support renaming the action methods by updating the name everywhere. It is a known limitation of the current refactoring integration. *** This issue has been marked as a duplicate of 106831 *** |
When you refactor a method that is annotated with a JSR-296 @Action (and thus used by UI elements) NetBeans fails to refactor the action due to it being burried inside a string token: SomeActionComponent.setAction(actionMap.get("someActionInTheActionMap")); This can be hard to spot since there is no warning or error of any kind, the application simply stops invoking any action.