All geek questions in one place

What is the point of defining multiple services in a single WSDL file

I understand that it makes sense to expose the same functionality (interface in WSDL 1.2, portType in WSDL 1.1) under different endpoints (ports in WSDL 1.1), depending on the underlying transport protocol (defined by the binding). But what is the point of putting the definitions of different services in one WSDL? Especially if each service provides only one operation?

For example, see the following WSDL file: http://seekda.com/cache?uri=http://score.itsc.uah.edu/services/catalog/SCOOPCatalogServices.wsdl&type=xml

The WSDL1.2 specification mentions that "WSDL 1.1 supports multiple services in a single WSDL file, which caused confusion among users." They resolve this by allowing "multiple services, each of which may have a different type of service." What does it mean - are there different types?

Maciej

+3
source share
2 answers

What is the point of defining multiple services in a single WSDL file?

In the same sense, why do you define several interfaces with various operations in an object-oriented language: to modulate your service.

, , . , .

: ! WSDL.

, ...

+3

, WSDL http://score.itsc.uah.edu/services/catalog/SCOOPCatalogServices.wsdl.

. , , SOAP 1.1 SOAP 1.2; , - .

WSDL, XMLSpy. <soap:operation/> soapAction.

+1

Source: https://habr.com/ru/post/1713279/

More articles:


All Articles