There are three ways how to refer batch artefact in job.xml file.

• Using @Name annotation
• Using fully qualified class name
• Using batch.xml

I noticed that the class name is not changed in batch.xml file during refactoring and the job.xml file become invalid for this reason.

There is a way how to avoid this problem. User can check the "Update fully qualified names in non-Java text files" option in Rename window, but this solution is not intuitive/is not user friendly I think.

In another case, when I don't use batch.xml and use the name comming from @Named annotation. The artefact is renamed in job.xml file even if the "Update fully qualified names in non-Java text files" option aren't selected. Non-Java text file (job.xml) is updated automatically in this case.

There is attached project that you can use to reproduce this problem.
BatchRenameManualTest.zip. Just try to rename Writer class.