The JAX-RPC specification talks about something called implicit and explicit service context.
JAX - RPC规范讨论了关于所谓的隐式和显式服务上下文方面的知识。
The explicit service context is represented as additional parameters appended to the service method calls.
显式服务上下文的表现形式是作为追加于服务方法调用的附加参数。
System architectures are designed as collections of services governed by inter-services protocols and explicit service-level agreements (SLAs).
系统体系结构设计成受到内部服务协议和外部服务级别协议（service-level agreement，SLA）管理的服务集合。
In the first case, that string is an explicit service level, for example GoldService, and in this case it is the CN of a verified, valid certificate.
在第一个实例中，字符串是一个直接的服务级别(例如GoldService)，在这种情况下它是已通过检验的、有效证书的CN。
The specification then describes how explicit service contexts are mapped into the remote interface of a service, whereas implicit contexts are typically not.
规范因此描述了显式的服务上下文如何映射到服务的远程接口中，而隐式的上下文通常却不能这样做。
Explicit separation of concerns between implementation of the service functionality (business logic) and enterprise data support logic.
服务功能(业务逻辑)的实现和企业数据支持逻辑的实现在关系上的明确分离。
Service transparency was provided by explicit interface and lookup, which provided decoupling between services and the interfaces between them.
由显式接口和查询提供的服务透明性，可以在服务和服务间的接口之间进行分离。
The approach ensured that service clients had no dependencies on the concrete services that implemented the explicit interfaces they invoked.
该方法能保证服务客户机对实现其调用的显式接口的具体服务不具有依赖性。
If a service supporting the required explicit interface was found in the local repository, a direct reference to the service object would be returned.
如果在本地存储库中找到了一个支持所需的显式接口的服务，将返回对该服务对象的直接引用。
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.
使用纯粹的抽象 C++显式接口类与真正的服务调用透明性是矛盾的，因为非 C++系统中的服务客户机需要备用的接口定义。
No explicit planning occurs; instead, the dependencies simply define the flow of service initiation, with parallelization implicit in the process.
没有进行显式的规划；相反，依赖关系简单地定义了服务初始化的流程，这个过程中隐含着并行化的操作。
Explicit separation of concerns between implementation of the service functionality (business logic) and enterprise data support logic (similar to the previous pattern).
服务功能(业务逻辑)和企业数据支持逻辑的实现在关系上的明确分离(和上一个模式相似)。
Service usage by more than one consumer is an explicit SOA design goal.
由多个使用者使用服务是明确的SOA设计目标。
Strictly speaking, it is not correct to refer to proxy mode services as deployments of existing services; there is no explicit reference to the ultimate receiver when a proxy mode service is set up.
严格来说，把代理模式服务作为现存服务的部署是不正确的，因为当代理模式服务被设置时，没有对最终接收者的引用。
The service context provided both local and remote discovery of services supporting required explicit interfaces.
服务上下文提供了本地和远程两种方式，用来发现为所需的显式接口提供支持的服务。
It is up to the container vendor (for either implicit or explicit context management) and the programmer (for explicit context management) to define the handlers to process the service context.
定义处理程序来进行服务上下文是由容器提供商(针对隐式或显式上下文管理)和程序员(针对显式上下文管理)决定的。
This usage model comprises 15 tool mentors that provide explicit instructions for using Rational Software Architect to identify, specify, and realize service solutions using the Rational SOMA method.
这个使用模型有15个工具顾问，他们会对使用Rational Software Architect来识别、指定和实现采用Rational SOMA的服务解决方案进行明确指导。
There are two different ways to define the use of SOAP header fields in a Web service, namely implicit and explicit headers.
在Web服务中有两种不同的定义SOAP 消息头字段用法的方法，即隐式消息头和显式消息头。
One option to ease this issue for the output service might be to have an explicit version parameter on the operations or an explicit version field on the complexTypes.
为输出服务简化这个问题的一个选择是在操作中增加显式的“version”参数，或是在“complexType”中增加显式的“version”字段。
Semantic templates for Web services request and response will establish an explicit contract between the service provider and the service requester.
Web服务请求和响应的语义模板将在服务提供者和请求者之间建立一个明确的协议。
An explicit consequence of this pattern (discussed on p. 255 of [Alur]) is to hide remoteness of the business service.
采用这种模式的一个明显的结果是([alur]在第255页的讨论)将隐藏商业服务的远程性。
One of the key characteristics of a RESTful Web service is the explicit use of HTTP methods in a way that follows the protocol as defined by RFC 2616.
基于REST的Web服务的主要特征之一是以遵循rfc 2616定义的协议的方式显式使用HTTP方法。
Ed from service provider details with well-defined interfaces supported by explicit interfaces, and proxy and invoker objects.
是利用经过良好定义的接口从服务提供者的细节中抽象出来的，这些接口由显式接口以及代理和调用程序对象提供支持。
By adding an explicit inter-domain trust between EU and NA, service ticket requests from Europe only require two hops.
通过在eu和na之间添加显式的域间信任，从欧洲请求服务票证的操作仅需要两次跳转。
The second responsibility is made explicit in the interface: the dependency that must be satisfied is the validation service dependency.
第二个职责在接口中被明确表达：必须满足的依赖项是验证服务依赖项。
Keep service interface and service implementation apart from each other and be very explicit about your implementation choices, especially the instancing model.
让服务接口和服务实现彼此分开，明确你的实现选择，尤其是实例化的模式。
A partial "service Generator" was written that generated skeleton code for proxy, invoker, and service classes from an explicit interface.
“服务生成器”的功能是根据显式接口为代理、调用程序和服务类生成框架代码，它已经被部分编写出来。
Any change to composite service requires explicit reprogramming of the service mediator.
对复合服务的任何改变都必须重新编写服务中介者的实现。
Any change to composite service requires explicit reprogramming of the service mediator.
对复合服务的任何改变都必须重新编写服务中介者的实现。
应用推荐