Web Service Software Factory 构架

         一、Web Service Software Factory 是微软在patterns & practices中提出的关于Web Service 的最佳实践
         二、首先来看看关于ASMX Service模板的解决方案框架图,有对于我们以后的学习有个全局上了解

因为我的e文不是很好，所以我把原文也发了上来,以免误人子弟
Service interface layer. This layer defines the operations of a service, the messages required to interact with each operation, and the patterns by which these messages interact—these patterns are referred to as message exchange patterns. The service interface layer contains a service contract, which describes the behavior of a service and the messages required as the basis for interaction. The service interface layer also contains a service adapter, which is used to implement the service contract and to expose this functionality on a certain endpoint.
服务接口层.这层定义业务服务,所需信息互动每次行动而这些信息和互动的模式-这些模式称为信息交流模式.服务接口层包含了服务协议,用来描述行为所需的信息和服务为基础的互动.服务界面层也包含了服务适配器,它是用来执行这一功能服务协议和揭露某个端点.
Business layer. This layer incorporates components that implement the business logic of the application. Simple services often require only a very simple business action, but services with more complex requirements may implement a Controller pattern or business rules for implementing service behavior. The business layer also includes business entities that are used to represent objects specific to a business domain. These entities can incorporate both state and behavior.
商务层.这一层包含商业逻辑元件,贯彻实施往往只需要一个非常简单的服务动作,但更为复杂的服务要求,则可能要实施控制器模式或业务实施细则的服务行为.业务层业务实体还包括用来向特定对象所代表的业务领域.这层也包括商务流程
Resource access layer. This layer contains the logic necessary to access data. The layer also contains service agents, which isolate the idiosyncrasies of calling diverse services from your application and can provide additional services, such as basic mapping between the format of the data exposed by the service and the format your application requires. Components to address cross-cutting concerns. These components address functionality common to multiple layers of the architecture.
资源接入层.这一层包含的数据获取所需的逻辑.该层也包含服务代理孤立的特质,从你的应用和服务多样化要求提供额外服务,测绘等基本数据格式之间的接触和服务形式的申请.关切组件处理跨领域的.
        三、服务工厂的核心

Data types. These are used to define the abstract data structures that form the basis for content within a message. These types are often reused by different operations of a service and even by different services.
数据类型.这些都是用来界定抽象数据结构,形成了信息内容的依据.这些不同类型的业务,往往再用一个服务,甚至不同的服务.
 Message types. These are used to compose complex messages from existing data types and primitive types.
消息类型.这些是被用来从现有的数据类型和原始类型组成的复杂消息.
Service contracts. These specify the operations that services support and the messages required for interacting with each operation.
服务合约.这些具体行动表示支持和服务所需的信息交互配合运作.
Service implementations. These are .NET Framework classes that implement service contracts.
服务执行。 这些是.NET执行服务合约的框架类。
Adapters. These use the EntityTranslator to translate between message types or data types and types required by the business actions before invoking the business action. 适配器.利用这些entitytranslator在所需的消息类型或数据类型的商业行为之前调用商业行为的类型之间的解释.
Entity translators. These transform between message or data types and business entities. The entity translator is an object that is tightly coupled to both the service interface and business layers, but at the same time provides loose coupling between them. This loose coupling prevents changes in one layer from forcing changes in the other layer.
实体翻译器.这些消息或数据类型之间的转换和业务主体.翻译器是一个实体对象就是紧耦合服务接口和业务都层,但同时规定,它们之间保持低耦合.这一低耦合的变化防止了从一个层变化到另一层.
Business actions. These organize business logic by procedures where each procedure handles a single request from the presentation layer.
业务行为.这些组织业务的逻辑处理程序,每个程序一个单一的请求套层.
BusinessEntity. This is a class used to represent a domain model entity within the business layer of the application.
业务实体,这是一个类用来代表业务域实体模型的应用层.
Repository. This is an intermediate object used to support interactions between business logic and the data access logic. 库.这是一个中间对象用来支持互动业务逻辑和数据存取逻辑.