webMethods and Intelligent Business Operations 10.2 | Administering Mediator | Mediator | REST to SOAP Transformation | Limitations
 
Limitations
The following limitations apply when you invoke REST-enabled SOAP services:
*Multi-root XML payloads are not processed because URL-encoded parameters are supported only for one level of elements.
For example,
<add>
<num1/>
<num2/>
</add>
The URL-encoded request corresponding to the XML is: http://<Context-path>/AddIntsService/add?num1=10&num2=9
An XML structured as follows is not processed:
<add>
<nums>
<num1/>
<num2/>
</nums>
</add>
*Only GET and POST HTTP methods are allowed.
*POST: Default content-type is application/json
*GET: Default content-type is application/url-encoded
*If you want to send a URL-encoded string to a POST request, add the content-type header to the native service.
*You cannot apply both the Enable REST Support action and WS-Security policies to a virtual service.
*The Integration Server service and XSLT transformations are applied only after converting the client’s REST request to SOAP request. Hence, they cannot be applied directly to a client’s request. XSLT and Integration Server services are applied on the SOAP request obtained after converting the REST request.

Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release