业务域驱动类的层次结构的一个简单例子。
A simple example of a business domain-driven class hierarchy.
图30显示lzdataset类的层次结构。
接口不是类的层次结构的一部分，虽然他们结合班工作。
Interfaces are not part of the class hierarchy, although they work in combination with classes.
这种方法的一个抽象是：使用闭包，不需要开发访问者类的层次结构。
One attraction of this approach is that with closures you do not need to develop the visitor class hierarchy.
它以类为基础，并根据类的层次结构和继承关系用链表来构造规则库。
On the basis of class and in accordance with the level structure and the inheritance relation of class, a rule base is constructed by using linked lists.
再次声明，这些特性只包含Hibernate和数据库，所以不会改变类的层次结构。
Once again, this feature involves only Hibernate and the database, and thus doesn't alter the class hierarchy.
如果这个类已经使用了一个超类，那么新生成的超类将把该类作为它的超类，并会保持类的层次结构。
If the class already USES a superclass, the newly generated superclass will have that class as its superclass, maintaining the class hierarchy.
另外，SchemaServer描述了结构性模型，用来以信息类的层次结构形式存储和交换信息。
Additionally, SchemaServer describes the structural models used to store and exchange information as a hierarchy of information classes.
它直接根据schema文档描述进行工作，生成与为文档所定义的元素类型和用法相匹配的类的层次结构。
It works directly from Schema document descriptions, generating a hierarchy of classes that matches the element types and usages defined for the documents.
但是，如果此类是可继承的，且之前已经有派生类的层次结构，则这些派生类可能需要访问此数据或代码。
However, if the class is inheritable and you expect a hierarchy of derived classes, it might be necessary for these derived classes to access the data or code.
为了最大限度地重用复杂的业务逻辑代码，您通常倾向于围绕系统的核心和主要业务功能设计类的层次结构。
To maximize the reuse of complex business logic code, you typically tend to design a hierarchy of classes around the core and primary business functions of the system.
使用这种方法，您可以将一个完整类层次结构映射成一个数据实体，而层次结构中所有类的所有属性都存储在这个实体中。
With this approach, you map an entire class hierarchy into one data entity, where all the attributes of all the classes in the hierarchy are stored.
类可以由那些拥有部件的类组成，允许您按照层级结构将一个系统逐步分解成任意的层次。
Classes can be composed of classes which themselves have parts, allowing you to hierarchically decompose a system to any arbitrary level.
显然，要修复这个问题，必须避免循环的类层次结构。
Obviously, to fix this problem, you must avoid the cyclic class hierarchy.
在这一模型中，您创建的所有变量都将引用在总的类层次结构中创建的对象。
In this model, any variable you create references an object that has been created from the overall class hierarchy.
缺点是每次在类层次结构的任何地方添加一个新属性时都必须将一个新属性添加到表中。
The disadvantages are that every time a new attribute is added anywhere in the class hierarchy a new attribute must be added to the table.
本文将提供一个小型类层次结构的例子，举例说明这个层次结构的概念。
This article gives you a simple example of a small class hierarchy to illustrate this concept.
这还不利于域类的设计，因为这个实用类现在必须位于对象层次结构的顶层，不允许您使用继承来整合常见行为。
It also hurts the design of your domain classes because this utility class must now sit at the top of your object hierarchy, not allowing you to use inheritance to consolidate common behavior.
将字段声明为受保护时，子类中的方法就有可能直接访问它们，这样就可能有效地增加类层次结构中的耦合。
When fields are declared protected, there is the possibility that methods in subclasses will directly access them, effectively increasing the coupling within a class hierarchy.
此类优化的另一个重要的例子是基于类层次结构的优化。
Another important example of this kind of optimization is class-hierarchy-based optimization.
整个类装入器集合形成了树状结构的层次结构，在其每个层次上都可装入不同类型的类。
The complete set of class loaders make up a tree-structured hierarchy with different types of classes loaded at each level.
域层次的静态视图为类结构和在使用案例中出现的它们的对象的关系建模。
The static view of the domain level models the class structure and their relationships of the objects witnessed in the use case.
它表示一个XML元素(来自清单1)，是类层次的基本结构。
This represents the one XML element (from Listing 1) and is the basic structure for the class hierarchy.
图6显示了一个更新过的持久性模型，用于将整个类层次结构映射成一个数据实体。
Figure 6 presents the updated persistence model for mapping the entire class hierarchy into one data entity.
我们将首先从一个更新过的层次结构图开始，它表明了哪个类提供了对HTTP连接的支持。
We'll start with an updated hierarchy diagram that indicates which class provides support for HTTP connections.
图1显示了GCF的类层次结构。
对等类装入不遵循传统的类装入器层次委托结构。
Peer class loading does not follow the traditional hierarchical delegation structure for class loaders.
您会注意到，TB_RIGHT表拥有保存right类层次结构的每个属性所需要的所有列。
You'll notice that the TB_RIGHT table possesses all the columns necessary to store every attribute of the Right class hierarchy.
前三个类构成了类层次结构的基类。
The first three classes constitute the base classes of the class hierarchy.
除了定义资源可以属于的层次结构类，OWL还允许表达资源的属性特征。
In addition to defining hierarchical classes that resources can belong to, OWL allows the characteristics of resources' properties to be expressed.
应用推荐