Considerations when refactoring mediation flow artifacts

WebSphere® Integration Developer provides a refactoring feature that handles dependencies when you rename, move, or change the namespace of an artifact. However, there are some things that you should take into consideration when refactoring.

Take into account the following when you refactor:
  • There are a number of ways that you can rename, move, or change the namespace of an artifact. The best way to perform these functions is through the refactor menu. If you use any other means, you will need to manually fix the dependent artifacts.
  • Before you perform a refactoring operation, make sure that you have no compile errors in the artifact that you are refactoring.
  • When you use the refactoring feature to rename an attribute of a business object, the xmx maps of dependent XSLT mediation primitives are updated to reflect the change. When you open the map in the XML mapping editor, you will see the change. However, you need to manually regenerate the xslt file from the updated xmx map by clicking the Regenerate XSL button in the mediation primitives properties view.

For information on the refactoring feature in WebSphere Integration Developer, see the Refactoring topic referenced in the related information.

Related concepts
Mediation services overview
Mediation Flow editor
Related tasks
Creating a mediation flow
Opening the Mediation Flow editor
Building mediation flows
Emitting common base events
Creating mappings for the XSL Transformation primitive
Selecting endpoints dynamically
Implementing custom mediation logic
Storing and using properties in the message context
Changing the value of mediation flow properties at runtime
Testing and debugging mediation modules
Related reference
Error handling in the mediation flow

Related information

Tutorial: Create a mediation flow
Samples: Mediation Flow editor
Contributing your own mediation primitive plug-in
Refactoring

Feedback
(C) Copyright IBM Corporation 2005, 2006. All Rights Reserved.