业务层也可以称为中间层或数据逻辑层，是应用程序的脉搏。
The business layer also can be called the intermediate layer or the data logic layer, the pulse of the application program.
学习自定义标记如何促进表示和业务逻辑之间的分离，同时还让您可以将动态数据合并到表示层。
Tune in then to learn how custom tags can facilitate the separation between presentation and business logic, while also letting you incorporate dynamic data into the presentation layer.
下一版本应该把重点放在服务接口，而不是数据访问和业务逻辑层。
The next version should focus less on the data access and business logic tiers and more on the service interface.
资源访问层，包含了访问数据所必需的逻辑。
The Resource access layer, which contains the logic necessary to access data.
许多用户都用自己的数据访问层，使用自己的API编写业务逻辑。
Many users have their own data access layer, with their own APIs, to which the business logic is coded.
这都是错误的观念，突然将业务逻辑与数据绑定层的选择结合在一起，最终必然会造成混乱导致出现问题。
These are both bad ideas — suddenly you've married your business logic to your choice of a data binding layer, and at some point that's going to catch up with you and cause problems.
这层负责运行应用程序的业务逻辑，获取相关数据(例如，运行SQL命令或者读取平面文件)。
This layer is responsible for running the application's business logic and getting the relevant data (for example, running an SQL command or reading a flat file).
对于第一种方法(将数据向业务逻辑进行移动)，您可以定义一个n层的缓存基础结构，并将它与GEE相关联。
For the first approach (bringing the data closer to the business logic), you can define an N-tier caching infrastructure and associate it with the GEE.
业务逻辑层包含值提供者，为支持Ajax的控件提供数据（请参见图5）。
The Business Logic Layer consists of the value providers that provide data to the Ajax-enabled controls (see Figure 5).
这种封闭的模型使Velocity能够提供分离的模板表示层，与任何应用程序业务逻辑或者数据管理代码清晰地划分开。
This closed model allows Velocity to provide a decoupled templating presentation layer, cleanly separated from any application business logic or data management code.
Slice不需要这类额外的模式层的信息，因为它根据持久性实例的逻辑名维护了实例和其原始数据库分区间的关联。
Slice does not require such additional schema-level information because it maintains the association between a persistence instance and its original database partition via its logical name.
应用程序表示层由jsp、servlet或portlet组成，它们从后端(或业务逻辑)获取程序数据，然后创建布局HTML(或其它标记语言)。
The application presentation layer is composed of JSPs, servlets, or portlets that get the program data from the back-end (or business logic) and create the layout HTML (or another markup language).
任意的数据源(文件、Web服务、定制存储、应用逻辑层等)。
Any data source (file, web service, custom store, application logic layer, etc).
一个基于SOA的EMR能够轻易地支持很多用户界面窗体，因为核心数据和业务逻辑功能与表现层是松耦合的。
An SOA-based EMR can readily support many forms of user interface because the core data and business logic functions are loosely coupled from the presentation.
这种体验比较接近混合架构，但实现起来更加简单，因为表示层和应用程序逻辑始终是针对本地数据库的。
This experience approximates the mixed architecture, but is simpler to implement because the presentation tier and application logic are always against the local database.
应用定制：在UI、业务逻辑和数据访问层，针对租户的元数据驱动的应用扩展。
Application customization: metadata driven application for tenant extensions at the UI, business logic and data access layers.
模型指数据，视图指表示层，而控制器指应用程序逻辑或业务逻辑。
Model refers to your data, View to your presentation layer, and Controller refers to the application or business logic.
该层的作用在于针对不同的数据存储技术，从业务逻辑中分离数据访问代码。
The power of this layer is in separating data access code from the business logic for disparate data store technologies.
因此，从概念上讲，DSL解决方案包括两个逻辑层：数据服务编排层(此层支持所引用的系统进程)和数据集成层。
So, conceptually, a DSL solution includes two logical tiers: a data services orchestration tier that supports the referred to system process and a data integration tier.
另外，被发送到远程数据源的查询由执行层根据缓存内容和高级空抑制逻辑进行进一步优化。
In addition the queries which are sent to remote data sources are further optimized by the execution layer based on cache content and advanced null suppression logic.
逻辑层将概念体系结构划分为在应用程序内扮演特定角色的组件，如表示层、应用程序逻辑层、业务流程层和数据访问层。
Logical tiers divide the conceptual architecture into components that play specific roles within the application, such as presentation, application logic, business processes, and data access.
表空间是数据库与实际容纳数据的容器对象之间的逻辑层。
A tablespace is a logical layer between the database and the container objects that actually hold the data.
这些底层数据调用整合到数据访问层中，对于业务逻辑是不可见的。
These underlying data access calls are thus consolidated in the data access layer and hidden from the business logic.
业务规则可以集中到业务逻辑层，该层充当表示层和数据访问层之间的数据交换的中间层。
Business rules are centralized into the business logic layer that serves as an intermediary for data exchange between the presentation layer and the data access layer.
而业务逻辑层则请求数据访问层处理数据持久性。
The Business Logic Layer, in turn, requests that the data Access Layer deal with data persistence.
数据建模有三层：概念、逻辑和物理。
There are three levels of data modeling: conceptual, logical, and physical.
逻辑视图中的三个软件层(表示层、业务层和数据层)是以代码形式被物理实现，并部署到这些节点上。
The three software layers in the logical view (presentation, business, and data) are physically implemented as code and deployed onto these nodes.
驱动程序层显示花费在执行数据库驱动器处理逻辑上的时间。
The driver layer shows times spent performing database driver processing logic.
展示层可以调用验证逻辑对表单提供的数据进行验证，然后再将该数据传递给域模型。
The presentation layer can call the validation logic on the data provided by a form before passing it to the domain model.
展示层可以调用验证逻辑对表单提供的数据进行验证，然后再将该数据传递给域模型。
The presentation layer can call the validation logic on the data provided by a form before passing it to the domain model.
应用推荐