Figure 1 shows the GCF class hierarchy.
图1显示了GCF的类层次结构。
Figure 30 shows the LzDataset class hierarchy.
图30显示lzdataset类的层次结构。
Using one data entity for an entire class hierarchy.
整个类层次结构使用一个数据实体。
Corrected class hierarchy of Liskov Substitution principle.
违反Liskov替换原则类结构图。
Consider the following class hierarchy for binary trees of ints.
考虑以下的int二元树的类层次结构。
Design fine-grained class hierarchy and coarse-grained database tables.
设计细粒度的类层次和粗粒度的数据表。
The first three classes constitute the base classes of the class hierarchy.
前三个类构成了类层次结构的基类。
Figure 24 shows the class hierarchy of some of the built-in components in OpenLaszlo.
图24显示OpenLaszlo中一些内置组件的类层次结构。
A class hierarchy always has a root class; this is a class with very general behavior.
类层次结构总会有一个根类(rootclass)，这是一个具有普遍行为的类。
The sole exception is the root of the Scala class hierarchy, Any, which has no parent.
唯一的例外是scala类层级结构中的根，Any，没有父类。
This article gives you a simple example of a small class hierarchy to illustrate this concept.
本文将提供一个小型类层次结构的例子，举例说明这个层次结构的概念。
For our RIGHT hierarchy, we'll use a single table (TB_RIGHT) to store the entire class hierarchy.
对于我们的RIGHT层次结构，我们只使用一个表(tb_right)来保存整体类层次结构。
This is exactly the sort of if-then-else chain that a properly constructed class hierarchy prevents.
这正好是那种一个正确构建的类层次所要防止的if - then - else链。
To access the Domino database in an efficient way, you need to create a domain-driven class hierarchy.
要以有效的方式访问Domino数据库，则需要创建一个域驱动的类层次结构。
This represents the one XML element (from Listing 1) and is the basic structure for the class hierarchy.
它表示一个XML元素(来自清单1)，是类层次的基本结构。
OOAD attempts to find the optimal set of objects and the most natural class hierarchy to implement them.
OOAD试图找到最优的对象和最自然的类继承来实现它们。
Figure 6 presents the updated persistence model for mapping the entire class hierarchy into one data entity.
图6显示了一个更新过的持久性模型，用于将整个类层次结构映射成一个数据实体。
Once again, this feature involves only Hibernate and the database, and thus doesn't alter the class hierarchy.
再次声明，这些特性只包含Hibernate和数据库，所以不会改变类的层次结构。
Even though the Estate class is nowhere to be found in our mapping file, it still exists in our class hierarchy.
即使在映射文件中找不到Estate类，它仍然存在于类层次结构之中。
In this model, any variable you create references an object that has been created from the overall class hierarchy.
在这一模型中，您创建的所有变量都将引用在总的类层次结构中创建的对象。
Spring's data access facilities automatically translate data-access exceptions into this exception class hierarchy.
Spring的数据访问功能自动将数据访问异常转换为此异常类层次结构。
Questions of design, such as how to design a class or a class hierarchy, are beyond the scope of this document.
设计方面的问题，例如如何设计类或组织类的层次，已经超出了本文档的范围。
For example, in Listing 10, I've defined an Ant task that builds a report for a class hierarchy, using the HierarchyBuilder.
例如，在清单10中，我使用HierarchyBuilder定义了一个为类层次构建报告的Ant任务。
You'll notice that the TB_RIGHT table possesses all the columns necessary to store every attribute of the Right class hierarchy.
您会注意到，TB_RIGHT表拥有保存right类层次结构的每个属性所需要的所有列。
Analogous to the getter implementation, it employs a TypeSetter class hierarchy for setting configuration values of various types.
与getter类似，它采用一个TypeSetter类层次用于设置不同类型的配置值。
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.
缺点是每次在类层次结构的任何地方添加一个新属性时都必须将一个新属性添加到表中。
You've actually seen one instance of another class hierarchy that also serves as a good illustration of the idea of extension by subclassing.
你已经看到了另一个类层次的实例，它很好的阐明了子类化的概念。
If the class already USES a superclass, the newly generated superclass will have that class as its superclass, maintaining the class hierarchy.
如果这个类已经使用了一个超类，那么新生成的超类将把该类作为它的超类，并会保持类的层次结构。
Spring defines a coherent data access exception class hierarchy (Figure 12) that you can use as a basis for your service- and DAO-layer exceptions.
Spring定义了一致的数据访问异常类层次结构（请参见图12），您可以将其用作服务和DAO 层异常的基础。
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.
使用这种方法，您可以将一个完整类层次结构映射成一个数据实体，而层次结构中所有类的所有属性都存储在这个实体中。
应用推荐