下面是一个使用单表策略映射超类和子类的示例。
Here is an example of mapping a super class and a sub class using the single table strategy.
他们可以利用预先构建的BPM内容和世界各地BPM专家及用户的贡献，从策略映射快速转移到流程执行。
They can leverage pre-built BPM content and contributions from BPM experts and users around the world to move quickly from strategy mapping to process execution.
这样，作业管理系统可以控制站点，并将站点任务策略映射到调度行为上，极大地改善集群的运行效率。
Thus, Job Management System can control the site, and make site's task strategy map up scheduling behavior, accordingly increasingly improve the running efficiency for the whole cluster.
基于此，提出了一种自适应增量策略处理机（APIP）的数学模型和实现方案，根据PEP在策略库的策略映射集合的变化情况，自动实现策略的增量分发。
This paper presents an Adaptive Policy Increment Processor(APIP) model and realization scheme, which can automatically accomplish policy increment distribution based on the change of the PEP's policy.
现在，请注意，每个映射策略怎样产生不同的模型。
Notice, now, how each mapping strategy results in a different model.
在前面场景中描述的XSLT映射中使用的所有策略在此处同样适用。
All of the strategies used in XSLT mapping described in the previous scenarios also apply here.
由于我们已经拥有数据库表，所以中间相遇映射是最适合的策略。
Since we also have database tables, a meet-in-the-middle mapping is the most appropriate strategy.
根据你的映射策略制定合理的选择查询并非易事；这需要你仔细调优业务需求，基于特定的数据场景制定合理的设计决策。
It is not easy to make a sound selection for your mapping strategy; it requires you to carefully tune your business requirements and make sound design decisions based on your specific data scenarios.
没有改变映射策略。
映射恰当的策略和模式。
简而言之，传统的映射策略忽略公路上的汽车：回退坏的模式变化并处理数据。
In short, traditional mapping strategies ignore the cars in the road: reversing bad schema changes and handling data.
为了应对可能的这种情况，如果在此事务策略中使用对象关系映射(ORM)框架，则应确保使用了版本验证功能。
To deal with this possibility, make sure you use versioning if you are using an object-relational mapping (ORM) framework with this transaction strategy.
另一方面，基于映射的框架可能工作得很好，但是要恰到好处地调整它们的映射策略，以便从对象生成需要的XML。
On the other hand, the mapping-based frameworks may serve you well, as long as you can tailor their mapping strategies enough to produce the XML you want from your objects.
为了使性能最大化和更加便利，目前的策略是从某一个表中提出元数据，先把一个类的实例映射到那个表上，用来初始化。
The current strategy for maximizing performance and convenience is to retrieve metadata for a particular table the first time an instance of the class that maps to that table is instantiated.
hrd[1]中的第9章“继承映射”已经说得很清楚了，所以我们将关注SQL生成和针对每个策略的调优建议。
Chapter 9 "Inheritance Mapping" in HRD [1] already has good coverage, so we will focus on SQL generation and tuning recommendations for each strategy.
通过定义类的映射文件，可以覆盖默认的绑定策略，并就类在XML中的表示方式对编排器提出建议。
By defining mapping files for your classes, you can override the default binding strategy and advise the marshaler how you'd like your classes to be represented in XML.
在创建表格工作流策略时，只有涉及表格步骤处理器的工作流步骤才在表格字段和工作流数据字段的映射中可见。
Only workflow steps with form step Processor are visible for the mapping of form fields and workflow data fields in the creation of a form workflow policy.
在一个业务策略和一个可实现的规则之间进行1对1的映射可能更容易让人理解。
Having a 1-to-1 mapping between a Business Policy and an implementable rule might be easy for individuals to understand.
图8显示了第三种映射策略的解决方案——将单个类映射成单个数据实体。
Figure 8 presents the solution for the third mapping strategy — mapping a single class to a single data entity.
这种方法允许表单策略向导自动映射所有字段。
Doing this allows the form policy wizard to automatically map the fields together.
工作流需要定义有与表格工作流策略中要映射的表格字段对应的数据字段。
The workflow needs to have the data fields defined that correspond to the form fields for the mapping in the form workflow policy.
我就使用这种策略来测试PetStore或or映射层。
随着你项目的进化，如果你要反复重新映射，那你可能也会采用该策略。
You probably will also resort to it if you have to reactively redesign your mapping strategy as your project evolves.
在我们第一个策略中，我们要看看如何映射我们的Person层次结构。
In our first strategy, we'll look at how to map our Person hierarchy.
我将示范的第一个将域类映射到遗留表的策略是使用静态mapping块。
The first strategy I'll demonstrate for mapping your domain class to a legacy table is using a static mapping block.
在本文中，我们试图向您提供一个相当简单的实现示例，演示Hibernate提供的三个映射策略。
In this article, we tried to give you a fairly simple implementation example for three mapping strategies Hibernate provides. In retrospect, each strategy has its advantages and drawbacks.
Hibernate允许在两个地方定义数据抓取策略，一处是在映射元数据中，另一处是在HQL或Criteria中覆盖它。
Hibernate allows you to define a fetching strategy at two locations. One is to declare it in the mapping metadata; the other is to override it in either the HQL or the Criteria.
选择Meet - in - the - middle映射策略，然后单击Next。
中介策略使用 WS-Policy格式，WS-Policy中使用的概念与提升属性中WebSphereESB定义的那些概念之间存在一种简单的映射。
Mediation policies use the WS-Policy format and there is a simple mapping between the concepts used in WS-Policy and those defined by WebSphere ESB in promoted properties.
中介策略使用 WS-Policy格式，并且在提升属性中，WS-Policy使用的概念和WebSphereESB定义的概念之间存在一种简单的映射。
Mediation policies use the WS-Policy format, and there is a simple mapping between the concepts used in WS-Policy and those defined by WebSphere ESB in promoted properties.
应用推荐