对于领域对象的依赖注入的新可能性。
The new possibility of Dependency Injection for domain objects.
系统中也没有领域对象。
第二步：按需进行依赖注入的富领域对象。
Step 2: Rich Domain Objects with on-demand dependency injection.
不需要横切领域对象。
它同时还包含了表示特定业务领域对象的业务实体。
It also includes business entities that represent objects specific to a business domain.
可以通过XML模式表示业务领域对象和它们的结构关系。
Business domain objects and their structural relationships can be well represented through an XML schema.
一个实体若想成为富领域对象不仅要包含状态，还得能调用业务服务。
For an entity to be considered a rich domain object it should not only contain state but also be able to call business services.
尽管继承映射是领域对象的一部分，出于它的重要性我们将它单独出来。
Although inheritance mapping is part of domain objects, we treat it separately due to its importance.
公共对象模型规范化(最重要的是在分类学和语义差异方面)多个领域对象。
A common object model normalizes (most importantly, in terms of taxonomy and semantic differences) multiple domain objects.
约束是定义在一个bean（领域对象）中的，因此校验逻辑离领域模型最近。
The constraints are defined in the bean (domain object) so the validation logic is close to the domain model.
这些方法只是Grails为你的领域对象所提供的众多动态方法的一小部分而已。
Those methods are just a small sampling of the many dynamic methods that Grails provides for your domain classes.
这个设置允许Grails在运行时使用你的领域对象同步更新数据库模式。
This setting allows you to have Grails update your database schema at runtime to synchronize it with your domain classes.
NakedObject应用中的领域对象是用户界面的核心，同时也是开发活动的焦点。
Domain objects in Naked objects applications form the core of the user interface, and are the focus of development efforts.
基于4.1节中对业务规则和设计的调优，你得到了一个用POJO来表示的领域对象的类图。
Based on the tuning of business rules and design in Section 4.1 you come up with a class diagram for your domain objects represented by the POJO. Our recommendations are.
后面将会提到，这种机制的技术基础是DDD，可以用一种优雅的方式将实体提升为富领域对象。
The mechanism for that, as will be explained further below, lays the technical foundation for DDD and allows entities to be promoted to rich domain objects in an elegant way.
要想使用领域设计方法，你就需要为实体类定义和构建资源库来实现领域对象的持久化。
Using a domain driven design approach you will need to define and build repositories for the entities that make up your domain.
NakedObjects是一种架构模式，也是一个以领域对象为中心角色的应用开发框架。
Naked objects is an architectural pattern and a framework for developing applications where domain objects takes a central role.
假设如果你有一大堆领域对象，你从最上层的Object类进行隐式选择查询，那该需要多长时间啊！
Imagine how long it would take if you had a large set of domain objects and you implicitly selected from the top object class.
如果你把用户界面设计成领域对象的直接反映，那么用户界面将强迫，同时也帮助你完善领域对象的行为。
And if you make your user interface a direct reflection of the domain objects, then this will both force and help you to make the domain objects behaviourally-complete.
实现该trait的领域对象只需实现getEntity方法即可，该方法的实现仅仅是返回一个自身引用
The domain object implementing this trait only has to provide the getEntity implementation, in which it simply returns a reference to itself
为了达成这一目标，需要一种透明的机制将服务注入到领域对象中，不管对象在何处实例化都该如此。
In order to achieve that there should be a mechanism to transparently inject services into domain objects, no matter where in the code they are instantiated.
将您的首个领域对象（DomainObject）命名为Application，如图6 所示。
Name your first Domain Object Application, as shown in Figure 6.
他建议以纯ddd方法开始，然后创建实现了领域对象的对象(POJOs或无状态beans)，并将它们暴露为服务。
He suggests starting from a pure DDD approach, then creating objects (POJOs or stateless beans) implementing domain objects and exposing them as services. As a result, he has created.
在业务分析和设计过程中，你应该将不同数据获取或修改分组放到不同的领域对象实体中，而不是使用这种抓取策略。
During business analysis and design, you should put different data retrieval or change groups into different domain entities instead of using this fetching.
而良好设计的领域对象（well designed domainobjects）定义的是一组基础对象，它们用于语义数据模型、构建服务、以及在它们之间传递信息。
Well designed domain objects, on the other hand, define a set of foundational objects that can be used for semantic data models, building services and passing information between them.
其中一些非常适合作为大学课程教科书，但是大部分，在我的观点来看，更适合于那些对特定对象技术领域需要不仅仅是粗略理解的专业人员。
Some are appropriate as college course textbooks, but most, in my opinion, are more suitable for working professionals who need a more than cursory understanding of a specific object technology area.
另一方面，对象领域模型还有自己的局限，特别在SOA环境中更是如此；在SOA环境中，跨越多个层次和系统的灵活性和解决方案是最为重要的。
On the other hand, the object domain model also has its limit, particularly in SOA environments, where flexibility and solutions spanning multiple layers and systems are of Paramount importance.
显示这些模型所需的数据消耗可用内存，通过导入附加对象领域来扩展一个项目将会增加内存的消耗。
The data required to represent these models consumes available memory. Extending a project by importing additional subject areas will increase the consumption of memory.
大部分传统OO系统和程序都包括对领域数据对象的层次结构进行操作的业务对象。
Most of the traditional OO systems and programs consist of business objects manipulating hierarchies of domain data objects.
最近，对象存储在云存储领域回归。
Object storage has made a comeback recently in the area of cloud storage.
应用推荐