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.
Unsure whether to file this as an enhancement or a defect issue: While doing large-scale structural refactoring in a set of web and library projects, I sometimes felt sort of frustrated seeing that, even though "Refactor" -> "Rename", applied on java classes and packages, does correctly change package and class names throughout other java classes relying upon them but leaves everything else (web.xml, logging configurations, possibly Spring-applicationContext - files, ...) untouched. Shouldn't, for the sake of usability, this automatically happen in course of the "rename" refactoring as well? So far, it seems doing a "Refactor" -> "Rename" in some more complex application just does half the job... ?
Many configuration files, such as web.xml, persistence.xml and spring application-context.xml (if you have the Spring module installed) are handled already, but a general xml refactoring is missing.
I have renamed via refactoring a class, which is included in applicationContext.xml of a Spring project. The refactoring did not propagate the change into the xml file and I had to change it manually. I have done this many times with many classes and the changes never propagated. I also have two modules (separate projects) and I moved classes and interfaces around. Both projects have their own contexts, one is importing the other one. No changes were propagated too. I was searching for a Spring module or plugin for NetBeans, but it seems that it should support it natively. This is not the case with my project.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss