Are there any recommendations for validating your various Spring XMLs for code changes such as renaming a class or removing a setter from a class? The concern is mostly related to the production XML, but for example WRT a name change, that name may be in multiple Spring files. I can evaluate the test XML easy enough by running the test suite and fixing any failures/errors, but it would be nice not to have to hit RuntimeExceptions to debug the production XML.
Dealing with XML config maintenance Page Title Module
Move Remove Collapse