IBM BPM, V8.0.1, All platforms > Programming IBM BPM > Enterprise Service Bus programming > Data Transformation > Business Object Map and Mapping mediation primitives
Comparison between the Mapping and BO Mapper mediation primitives
There is some overlap between the capabilities of the BO Mapper and the Mapping (previously called the XSL Transformation) mediation primitives. The following table summarizes the different capabilities of each.
Use Mapping when Use BO Maps when You have an existing stylesheet or want to use custom XSLT in the map. You have an existing BO Map or submap. You want to use XPath expressions inside the map You want to use the relationship service (particularly dynamic relationships). You want to use Java™ snippets that use the DOM API to access or update data. You want to use Java snippets that use the BO API (SDO API) to access or update data. You want to use built-in XPath or EXSLT functions to access or modify data. You want to order the completion sequence for the transforms. You want to combine contents from more than one array (repeating element). BO Maps can be faster when used with WebSphere Adapters, because the BO Maps work directly with the SDO API. When performance is important and the advanced functions offered by XSLT are not required, the BOMapper mediation primitive should always be used.
When performance is important, use the BOMapper mediation primitive or set the Mapping mediation primitive to use the Business Object Map engine.
The XSL Transformation mediation primitive was renamed to the Mapping mediation primitive in Version 8 when the ability to switch between XSL stylesheets and BO Maps was added to the mediation primitive.