Skip to content

Commit e3c71a6

Browse files
Merge pull request #260563 from dlepow/docs-editor/api-management-api-import-rest-1701910386
Update api-management-api-import-restrictions.md
2 parents 899abf4 + 640b932 commit e3c71a6

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

articles/api-management/api-management-api-import-restrictions.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -246,11 +246,14 @@ This message type is not supported.
246246
- Types defined recursively aren't supported by API Management.
247247
- For example, refer to an array of themselves.
248248

249-
### Multiple Namespaces
249+
### Multiple namespaces
250250
While multiple namespaces can be used in a schema, only the target namespace can be used to define message parts. These namespaces are used to define other input or output elements.
251251

252252
Namespaces other than the target aren't preserved on export. While you can import a WSDL document defining message parts with other namespaces, all message parts will have the WSDL target namespace on export.
253253

254+
### Multiple endpoints
255+
WSDL files can define multiple services and endpoints (ports) by one or more `wsdl:service` and `wsdl:port` elements. However, the API Management gateway is able to import and proxy requests to only a single service and endpoint. If multiple services or endpoints are defined in the WSDL file, identify the target service name and endpoint when importing the API by using the [wsdlSelector](/rest/api/apimanagement/apis/create-or-update#wsdlselector) property.
256+
254257
### Arrays
255258
SOAP-to-REST transformation supports only wrapped arrays shown in the example below:
256259

0 commit comments

Comments
 (0)