SOAP to message header mapping
SpEL expression that will be used to fill the outgoing SOAP header of consumed web service requests and published web service responses.
Optional ; if empty, this header mapper will not add a SOAP header to outgoing web service requests or responses.
Example SpEL expression:
'<erp:authentication xmlns:erp="http://www.example.com/ns/erp/1.0/"> <erp:user>' + erp_user + '</erp:user> <erp:passphrase>' + erp_passphrase + '</erp:passphrase> </erp:authentication>'Note that the root object of the SpEL evaluation context is always the message's header, so
erp_user
in the above example will be replaced with the value of the erp_user
message header.
Also note that it's possible to use ${}
property placeholders in this SpEL expression. These placeholders will be resolved first, before the SpEL expression is evaluated.
Mapping between header names and XPath expressions to determine the header values when processing the incoming SOAP header of consumed web service responses and published web service requests.
Optional ; if empty, this header mapper will not process the SOAP header of incoming web service requests or responses.
Example XPath expressions:
erp_user -> erp:authentication/erp:user erp_passphrase -> erp:authentication/erp:passphraseNote that the root XML node of the XPath evaluation context is always the
<soap:Header>
element, so the above example is the exact reverse of the SpEL expression example (provided that the erp
namespace prefix is correctly specified).
Also note that the XPath expression is always evaluated as a string value: if the resulting string is empty, the message header is not added to the message.
Header name
Name of the message header to create on the message.
If a header with this name already exists, it will be overwritten with the new value.
Required
XPath expression
XPath expression to determine the value for the message header. The root XML node of the XPath evaluation context is always the <soap:Header>
element.
Example XPath expression:
erp:authentication/erp:userNote that the XPath expression is evaluated as a string value: if the resulting string is empty, the message header is not added to the message.
Required
Namespace prefix
Optional namespace prefix that is used in the XPath expression specified above.
For example, in the XPath expression mentioned in the previous help text the namespace prefix erp
is used.
Optional
Namespace URI
Optional namespace URI that is referenced by the namespace prefix specified above.
For example, the namespace prefix mentioned in the previous help text could point to the http://www.example.com/ns/erp/1.0/
namespace URI.
Optional
Id
Name that uniquely identifies this flow component.
Required