Service Binding- Response Context

Response Context maps data from the Set Context Activity to the response message.

Data Source

Displays the data source schema tree for the output context parameters. All elements in this tree are available to drag and drop into the XPath Expression field.

The following table shows the response message entities:

Elements of Set Context/ Response Message Description
Headers Headers of the response message.
  • pragma: Includes implementation-specific directives that might apply to the receiver.

    For more information about this field, see the HTTP specification at w3.org.

  • location: Redirects the receiver to a location other than the Request-URI for completion of the request or for identification of a new resource.
Dynamic Headers The dynamic header is an additional header parameter to add runtime headers to the outgoing HTTP messages. The DynamicHeaders consists of the following information:
  • Name: the name of the header
  • Value: the value of the header
Headers

The fields of the header specified on the Input Headers tab.

Undescribed Headers Undescribed headers of the response message.
mimeEnvelopeElement Information about the attachements that are present in the response message. Individual attachment information is populated under one mimepart element. All attachments are configured as SwA unbound attachments.
Note: If the attachment size increases the threshold value configured at the binding level, the file name of the serialized attachment is populated.
mimeHeader

This element contains the mime header for each mimePart. Mime headers can contain the following information:

  • content-disposition — To suggest a filename for an attachment, use "*;filename=<filename>" in this element.
    Note: HTTP servers may alter or choose to ignore the suggested name.
    • content-type
    • content-transfer-encoding
    • content-id
    • other mime header information
    For more information about MIME headers and their syntax, see http://www.faqs.org/rfcs/rfc2045.html .

When the content type is specified as "text/*" (for example, "text/xml"), the attachment content is expected to be in either the textContent input element or the file name storing the attachment is expected to be in the fileName input element.

When the content type is anything other than "text/*", the attachment content is expected to be in either the binaryContent input element or the file name storing the attachment is expected to be in the fileName input element.

binaryContent | textContent | fileName

This element contains the mime attachment. The element can be one of the following:

  • binaryContent — content of the attachment when the attachment is binary data.
  • textContent — content of the attachment when the attachment is text data.
  • fileName — the file name of the attachment written to the disk.