IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Defining and transforming data > Transforming data > Transforming data using XML maps > XML map limitations
DataPower limitations
Limitations when developing services for DataPower in IBM Integration Designer.
Mapping between complex types
An XML map that contains a mapping between an input complex type and an output complex type cannot be run directly in DataPower. The complex type to complex type map must be called as a submap by a map that has an element to element mapping.
Library dependencies
Library dependencies are not supported for DataPower libraries. You cannot share artifacts between two DataPower libraries, or between a DataPower library and a regular library.
SOAP messages
The XSLT file that is generated by the mapper cannot transform a SOAP request. If you want to transform SOAP messages, you must add the SOAP transformation step in DataPower.
Business Objects
When you create a business object for DataPower, create the business object as a global element, by selecting the option Create the business object as an element in the New Business Object wizard.
Synchronizing changes between Integration Designer and DataPower
In Integration Designer, the main artifact for mapping is the XML map, and the XSL file is generated based on this map. This means that if you create an XSL file in Integration Designer, change it in DataPower, and then bring the XSL file back into Integration Designer, the changes made to your XSL file in DataPower will be lost the next time the XSL is generated.
For example, when you do a project clean.
If you want to change the XSL file on DataPower, you must write the code using a custom xslt transform and then make any changes in the custom code.