Limitations
The following limitations apply when you perform a SOAP to REST transformation:
![*](chapterTOC_bullet.png)
When the API provider defines the mapping for the SOAP operation to the REST resource or method,
API Gateway allows him to specify either the path and the query parameters or the body but not both. These mappings are used when transforming the incoming REST request to the SOAP request.
![*](chapterTOC_bullet.png)
If both path and query parameters and body are sent in the incoming REST request, then the path and the query parameters are ignored.
![*](chapterTOC_bullet.png)
If your REST resource accepts the
text/xml content-type, then you cannot modify the default resource path and resource name automatically generated by the system. This name must be same as the SOAP operation name. However, this limitation is not applicable for other content-types.
![*](chapterTOC_bullet.png)
The HTTP method filters of the global policy are not applicable to the REST transformed method of the SOAP API.
![*](chapterTOC_bullet.png)
The REST (REST transformed SOAP operations) resources do not appear as general REST resources when filtered in the
Scopes section of the API in
API Gateway.
![*](chapterTOC_bullet.png)
You cannot apply the
Inbound Authentication-Message policy to the SOAP operation enabled as REST.
![*](chapterTOC_bullet.png)
The SOAP services that have Web Services Interoperability Organization (WS-I) non-compliant WSDLs cannot be REST-enabled.