Creating mappings for the XSL Transformation primitive

When the message types of source and target operations do not match, you need to transform the source message type so that the target operation can receive it. The XSL Transformation primitive uses an XSL style sheet to map source and target message types. This topic describes how to create the XSL stylesheet.

In the Mediation Flow editor, you will be unable to connect primitives or nodes whose message types are different; you will see an error on the input terminal of the target node indicating that the terminal types are incompatible. In this case, you need an XSL Transformation primitive, as shown in the following image:
Picture of connection error message

The XSL Transformation primitive uses an XSL style sheet that contains the information required to map between two message types. You can either select an existing XSL style sheet, and optionally edit it, or create a new one. You create a new XSL style sheet by generating it from an XML map. You can either select an existing XML map, and optionally edit it, or create a new one using the XML Mapping editor.

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
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
Considerations when refactoring mediation flow artifacts

Related information

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

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