组件的接口和引用没有指定组件如何实现其服务。
A component's interface and references do not specify how the component implements its service. Rather, the service is implemented using one of several available technologies.
连线的源端的引用接口必须与目标组件的接口相符。
The interface of the reference at the source of the wire must match the interface of the target component.
产品组件的接口，包括内部和外部的，都是兼容。
The product-component interfaces, both internal and external, are compatible.
图10显示了ProcessOrder组件的接口。
Figure 10 shows the interface for the ProcessOrder component.
图12显示了CustomerInformation组件的接口。
Figure 12 shows the interface for the CustomerInformation component.
我们曾指出，引用的接口必须与它所连线到的组件的接口匹配。
We pointed out that the interface of a reference must match the interface of the component to which it is wired.
将这个组件的接口重命名为translation_library。
Rename the interface present in this component to translation_library.
我们还更改了ShippingTask组件的接口，以便返回这个新业务对象。
We also changed the interface for the ShippingTask component to return this new business object.
在后面描述的示例J2EE应用程序中，我们将看到如何改变组件的接口以便同时托管。
In the sample J2EE application described later, we will see how changes to component interfaces can be designed for co-hosting.
对于使用服务组件的用户，所关注的是组件的接口，因为它规定了组件的使用方式。
To users of a service component, all that matters is its interface, which dictates how to use it.
包容时外部组件包含内部组件的接口，聚合时外部组件直接向外公开内部组件的接口。
Containing component incorporates the interface of inner one, and aggregating component directly publishes the interface.
然而，发货组件的接口有一个名为ship的操作，并且两个操作的参数具有不同的名称。
However, the interface for the shipping component has an operation called ship, and both operations have different names for their parameters.
在您组装模块时，您可完全灵活地组装可重用的部件，前提是其引用与目标组件的接口相匹配。
As you assemble your modules, you have complete flexibility to assemble reusable parts, provided the references match the interfaces of the destination component.
在这种情况下，概念模型仍然指导组件中的业务类型和通过组件的接口传递的业务类型的定义。
In this case, the conceptual model still guides the definition of business types within the component and of those passed through the interfaces of the components.
如果组件的接口与引用所需的接口相匹配，那么可以将一个组件的任何引用连接到任何其他的组件。
You can wire any reference of one component to any other component, provided the component's interface matches the interface required by th reference.
与此类似，将基于类型对资源进行归类：业务对象位于DataTypes下，而每个组件的接口位于 Interfaces 下。
Similarly, it categorizes your resources by type: your business objects are under Data Types and the interfaces for each component are under Interfaces.
当引用和组件具有不同的接口时，您将使用此方法。
You use this method when the reference and component have different interfaces.
这个包中包含所有构成命名权限组件的类和接口。
This package contains all the classes and interfaces that comprise the naming authority component.
本文研究了远程组件和服务的接口设计。
This article investigated interface designs for remote components and services.
为标准组件的标准接口。
现在，我们的SCA组件具有接口，但没有实现。
We now have an SCA component with an interface, but no implementation.
会话或实体e JB组件的远程接口提供了位置独立性。
Remote interfaces to session or entity EJB components provide location independence.
我们主要关注构建组件所需的接口。
通过合作伙伴获得的外部服务和组件的服务与接口。
Services and interfaces for external services and components available through partners.
用于定义组件和接口的公共方法或公共语言。
A common approach, or common language for defining components and interfaces.
分布式服务层：在本层中，目标是指定为JMXManager组件提供的接口。
Distributed Services Level: In this level, the aim is to specify the interfaces that provide for JMX Manager components.
在右边面板展开DetailsProperties；选择您想要测试的组件、服务接口和相应的操作。
On the right panel, expand Details Properties; select the component, service interface and corresponding operation you want to do testing.
在您的流程所属的组件上的每个接口都将有一个接口合作伙伴。
There will be one interface partner for each interface on the component for which your process belongs.
组件模型通过说明组件提供的接口以及组件如何在整个系统解决方案中彼此依赖对组件进行描述。
The component model describes the components through the interfaces that they provide, as well as how components depend on each other in the overall system solution.
对于您刚才选择该组件所要支持的接口，现在您将实现该接口的操作。
Now you will implement the operation of the interface you just selected that this component will support.
应用推荐