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/jsonGET: Default content-type is
application/url-encodedIf 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.
