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.
Customized (rename only subset) refactoring from WSDL/Schama always renames all found strings. Steps to reproduce: - Create Synchronous sample project. - Open xsd file in 'Schema' mode. - Select Complex Types > simpleProcess > sequence > paramA. - Invoke popup menu item 'Refactor > Rename...'. - In appeared 'Rename' dialog enter some new name and press 'Next' button. - Window 'XML refactoring' opens. - Notice that there are found 2 places in bpel code for rename. - Uncheck the checkbox for 1st of them. - Press 'Do Refactoring' button. - Open bpel source and noticeed that all 'paramA' strings were renamed.
The problem is that refactoring engine requests to do renaming in all cases whether check box is set or not. The same situation with wsdl file: add message and set element from xsd to its part, do rename for the element, uncheck check box, do refactoing, open wsdl file: part has renamed element. Refactoring engine should process state of check boxes correctly.
Fixed. Cleaned up CheckNode constructors and their usages. /cvs/xml/refactoring/src/org/netbeans/modules/xml/refactoring/ui/j/ui/Attic/CheckNode.java,v <-- CheckNode.java new revision: 1.1.2.5; previous revision: 1.1.2.4 /cvs/xml/refactoring/src/org/netbeans/modules/xml/refactoring/ui/readers/Attic/WhereUsedReader.java,v <-- WhereUsedReader.java new revision: 1.1.2.16; previous revision: 1.1.2.15
The checkbox fix to persist user selection has been integrate, however the test case still fail due to further change in bpel refactoring engine. See attached patch. Reassig to bpel/refactoring. Note that keyword REGRESSION is very dubious. Base on the needed fixes (both in refactoring checkbox UI and bpel refactoring engine, I doubt that this ever work before even for xsd or wsdl usage components.
Created attachment 33925 [details] proposed patch to bpel refactoring engine
fixed.
fixed
Could reproduce the issue with build from 2006.10.04 with steps from description Reopening the issue
Fixed in both branches.