在这种情况下，我们使用一个抽象的类，来定义服务接口以及预期功能的操作，如图3所示。
In this case, we use an abstract class to define the service interface and operations of the exposed capabilities, as shown in Figure 3.
第一部分定义了服务的抽象接口，用端口类型（port type）表示，它包含操作集合（也就是业务功能）。
The first defines the abstract interface of a service, represented by port types, which contain collections of operations (that is, business functions).
这项端口支持组合结构的定义，这种结构中清晰但是抽象的接口，定义了“提供的”服务，或者客户所“需要的”服务。
These ports support the definition of composite structures with clear but abstract interfaces that define the services "provided" to, or "required" by your customers.
服务通信、交互和执行抽象都已完成，因此下一个步骤就是在服务间建立经过良好定义的接口。
Service communication, interaction, and execution abstraction were in place, so the next key step was to establish well-defined interfaces between services.
使用纯粹的抽象 C++显式接口类与真正的服务调用透明性是矛盾的，因为非 C++系统中的服务客户机需要备用的接口定义。
The use of pure abstract C++ explicit interface classes worked against true service invocation transparency, because service clients on non-C++ systems required alternative interface definitions.
它的编程接口严格基于WSDL端口类型定义的抽象服务接口。
Its programming interface is strictly based on the abstract service interface defined by the WSDL port type.
支持接口的每项服务或代理必须继承定义该接口的抽象基类。
Each service or proxy that supported an interface was required to inherit from the abstract base class that defined the interface.
Web服务背后的概念帮助您使用抽象的接口设计松散耦合的服务，这样就可以把服务实现与服务定义分开。
The concepts behind web services help you design loosely coupled services with abstract interfaces, thus decoupling service implementation from service definition.
是利用经过良好定义的接口从服务提供者的细节中抽象出来的，这些接口由显式接口以及代理和调用程序对象提供支持。
Ed from service provider details with well-defined interfaces supported by explicit interfaces, and proxy and invoker objects.
是利用经过良好定义的接口从服务提供者的细节中抽象出来的，这些接口由显式接口以及代理和调用程序对象提供支持。
Ed from service provider details with well-defined interfaces supported by explicit interfaces, and proxy and invoker objects.
应用推荐