Rational Developer for System z

Refactoring

Refactoring is the process of updating references to an entity when it is renamed, such as a renamed message file (also called a message definition file), renamed message, or a renamed part of a message.
For example, if you rename the message file MsgFile_01.sfmxsd to MsgFile_02.sfmxsd, and you choose to do refactoring, then Enterprise Services Tools does the following:
  1. It searches every file in the service flow project looking for a reference to the message file MsgFile_01.sfmxsd.
  2. If it finds such a reference, it changes the value of the reference to the new name MsgFile_02.sfmxsd.

Similarly, when you rename a single message or a part of a message, and you choose to do refactoring, then Enterprise Service tools updates all the references to the renamed entity in the current service flow project.

Usually, you want to do this refactoring. In the preceding example, consider what happens if the existing references are not updated. Each of these references still has the value MsgFile_01.sfmxsd. And there is no such entity in the service flow project any longer -- it has been renamed to MsgFile_02.sfmxsd. Therefore all the references to MsgFile_01.sfmxsd are broken. Moreover, if you forget about the broken references and later create another message file named MsgFile_01.sfmxsd, then all of the broken references to MsgFile_01.sfmxsd suddenly become valid. But this might not be what you intended!

However, there might be situations in which you want to rename a message file, a message, or a part of a message without refactoring. (But it is hard to think of such a situation.)


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)