inboundTransformationStrategy
Strategy that customizes the conversion of an incoming payload by a processor (e.g., string to object). Should be used when the processor’s default conversion logic cannot be used.
See the Payload Types documentation for more details and examples.
Properties
Name | Summary |
---|---|
|
Optional. Signifies a string transformation using the given character encoding. When transforming from binary to an object, binary data is first transformed to a string. This binary/string decoding defaults to |
|
Optional. Used to transform binary or string data to a JSON compliant object (e.g., |
|
Optional properties to use when transforming to strings. Uses a simple jdk-format for adding property values. |
|
ID of a WSDL or XSD specification following the pattern This property is optional and only relevant for conversions from XML documents to JSON compliant. It can be used to ensure that elements in JSON compliant representations of XML documents are aligned with the requirements specified in the XSD (e.g., correct representation of XML list elements). |
|
Mapping of prefixes to namespaces in the XML representation of inbound payload. The special Defining the prefix mappings here is highly recommended if you are doing any processing of the JSON compliant payload, since it is the only way you can mandate the prefixes yourself. Namespaces not defined here will have automatic prefixes in the form |