您也可以使用Scala的类型接口。
注重类型接口的编程技术。
Programming technique that focuses on the interface to a type.
弱类型接口和业务对象。
从应用程序的角度来看，类型接口是这些类最有趣的部分。
The type interfaces are the most interesting of these classes from the application program standpoint.
而且，即使采用泛型方式实现的服务也可以提供强类型接口定义。
And even a generically implemented service can provide a strongly typed interface definition.
动态api场景并不要求为数据模型中的对象生成类型接口、工厂类或实现类。
A dynamic APIs scenario does not require the generation of a typed interface, factory class, or implementation class for the objects in your data model.
如上面所示，在不能或不应使用生成的代码的情况下，可以采用松散类型方式实现强类型接口。
And as shown above, a strongly typed interface can be implemented in a loosely typed way in situations where generated code cannot or should not be used.
例如，提供消息记录功能的中介不需要强类型接口，因为它只记录其所接收到的所有消息的内容。
For example, an intermediary that provides logging of messages does not need a strongly typed interface, because it simply logs the content of any message that it receives.
匹配连接器必须是清洁的，必须满足连接器类型接口，并且必须符合相应的扭矩技术指标。
Mating connectors must be clean, must meet connector type interface, and must be tightened to the appropriate torque specification.
该系统采用直观、方便的参数编程方法，可以编写和输出H型钢各类型接口端头的切割程序。
This system adopts parametric programming method to program and output CNC cutting program for various interface ports of H-type section steel.
应该考虑对遗留代码进行重构，以确保接口为强类型；或构建中介，以使用强类型接口包装弱类型接口。
You should consider either refactoring your legacy code to ensure that interfaces are strongly typed or building a mediation that will wrapper the weakly typed interface with a strongly typed one.
由于接口和这些接口使用的业务对象对流程或任务的所有版本都必须完全相同，因此应该考虑使用弱类型接口。
Because interfaces and business objects used by these interfaces must be identical for all versions of a process or task, consider using weakly-typed interfaces.
通过结合对象初始化器和类型接口，我们可以生成一个简单的数据存储对象，而不需要定义相应的类或结构。清单5 - 24演示了一个例子。
By combining object initializers and type inference, we can create simple data-storage objects without needing to define the corresponding class or struct. Listing 5-24 shows an example.
此实例与静态数据api创建的实例的主要区别在于，该实例类型为commonj .sdo . DataObject而不是表示数据对象的类型接口。
The key difference between this instance and one created using static data APIs is that the instance type is commonj.sdo.DataObject and not a typed interface representing the data object.
这个服务器类型为接口提供了现有电话环境。
This server type provides the interface with the existing telephony environment.
既然这样，我为什么要在这里提及数据类型和接口呢？
数据类型和接口已经生成，并放在您的项目文件夹中。
Data types and interfaces are generated, and placed into folders for your project.
事实上，分类器是一个更为一般的概念，它包括数据类型和接口。
In fact, a classifier is a more general concept, which includes data types and interfaces.
对于系统中定义的每个操作类型，此接口都具有三个单向方法。
This interface has three one-way methods for each type of action defined in the system.
定义服务意味着为它创建一个项目并创建说明详细信息(如名称空间和端口类型(接口)名)的WSDL文件。
Defining your service means creating a project for it and creating a WSDL file specifying details, such as the namespace and port type (interface) name.
有两种类型的变量：数据类型和接口。
关于何时、以及如何高效地在系统结构图中使用数据类型和接口的完整讨论，不在本文的讨论范围之内。
A complete discussion of when and how to use data types and interfaces effectively in a system's structure diagrams is beyond the scope of this article.
正如我在前面指出的，最好避免使用泛型字符串类型的接口。
It is best to avoid generic string type interfaces, as I pointed out earlier.
协作角色的类型通常是接口。
The types of the collaboration roles generally are interfaces.
这个结构还有其他字段，比如查询类型、对象uuid、接口id等等。
This structure also has other fields like inquiry type, object UUID, interface ID among others.
为此，必须在游戏和游戏外服务之间提供某种类型的接口。
To do this, you have to provide some type of interface between the game and out-of-game services.
在我所遇到的大多数实际场景中，强类型服务接口更为适用。
In most real life scenarios that I have encountered, a strongly typed service interface is a better fit.
这个元模型（见图2）描述组件类型、接口和数据结构11。
This metamodel (Figure 2) describes component types, interfaces, and data structures 11.
SCA在接口类型方面可扩展。
对于数据类型的接口(业务对象)，部分名称是可选的。
For data typed interfaces (Business Objects), the part name is optional.
应用推荐