使用Apworks开发基于CQRS架构的应用程序（八）：应用程序的配置与编译

Apworks使用配置文件来启动整个系统。在上文中也能够看出，WCF服务在启动时，同时也启动了Apworks系统。所以，本节简要介绍这个WCF服务针对Apworks的相关配置节内容。

双击TinyLibrary.Services项目的web.config文件，根据下面的XML代码编辑该文件。

<?xml version="1.0"?>
<configuration>

  <configSections>
    <section name="apworksConfiguration"
             type="Apworks.Config.ApworksConfigHandler, Apworks"/>
    <section name="unityConfiguration"
             type="Microsoft.Practices.Unity.Configuration.UnityConfigurationSection, Microsoft.Practices.Unity.Configuration"/>
  </configSections>

  <apworksConfiguration>
    <application bootStrapper="Apworks.Application.BootStrapper, Apworks"/>
    <objectContainer provider="Apworks.ObjectContainers.Unity.UnityContainer, Apworks.ObjectContainers.Unity" section="unityConfiguration"/>

    <generators>
      <generator name="defaultIdentityGenerator" kind="Identity" type="Apworks.Generators.SequentialIdentityGenerator, Apworks"/>
      <generator name="defaultSequenceGenerator" kind="Sequence" type="Apworks.Generators.SequentialIdentityGenerator, Apworks"/>
    </generators>

    <handlers>
      <handler name="TinyLibraryCommandHandlers"
               kind="Command"
               sourceType="Assembly"
               source="TinyLibrary.CommandHandlers"/>
      <handler name="TinyLibraryEventHandlers"
               kind="Event"
               sourceType="Assembly"
               source="TinyLibrary.EventHandlers"/>
    </handlers>

  </apworksConfiguration>

  <unityConfiguration>
    <container>
      <register type="Apworks.Events.Serialization.IDomainEventSerializer, Apworks"
            mapTo="Apworks.Events.Serialization.DomainEventXmlSerializer, Apworks">
      </register>

      <register type="Apworks.Storage.IStorageMappingResolver, Apworks"
                  mapTo="Apworks.Storage.XmlStorageMappingResolver, Apworks"
                  name="DomainEventStorageMappingResolver">
        <constructor>
          <param name="fileName" value="DomainEventStorageMappings.xml"/>
        </constructor>
      </register>

      <register type="Apworks.Events.Storage.IDomainEventStorage, Apworks"
                mapTo="Apworks.Events.Storage.SqlDomainEventStorage, Apworks">
        <constructor>
          <param name="connectionString"
value="Data Source=.\SQLEXPRESS;Initial Catalog=TinyLibraryEventDB;Integrated Security=True;Pooling=False;MultipleActiveResultSets=True;"/>
          <param name="mappingResolver">
            <dependency type="Apworks.Storage.IStorageMappingResolver, Apworks" name="DomainEventStorageMappingResolver"/>
          </param>
        </constructor>
      </register>

      <register type="Apworks.Bus.ICommandBus, Apworks" mapTo="Apworks.Bus.DirectBus.DirectCommandBus, Apworks.Bus.DirectBus">
        <constructor>
          <param name="dispatcher">
            <dependency type="Apworks.Bus.IMessageDispatcher, Apworks"/>
          </param>
        </constructor>
        <lifetime type="ContainerControlledLifetimeManager"/>
      </register>

      <register type="Apworks.Bus.IEventBus, Apworks" mapTo="Apworks.Bus.DirectBus.DirectEventBus, Apworks.Bus.DirectBus">
        <constructor>
          <param name="dispatcher">
            <dependency type="Apworks.Bus.IMessageDispatcher, Apworks"/>
          </param>
        </constructor>
        <lifetime type="ContainerControlledLifetimeManager"/>
      </register>

      <register type="Apworks.Bus.IMessageDispatcher, Apworks" mapTo="Apworks.Bus.DirectBus.DirectMessageDispatcher, Apworks.Bus.DirectBus">
        <lifetime type="ContainerControlledLifetimeManager"/>
      </register>

      <register type="Apworks.Repositories.IDomainRepository, Apworks" mapTo="Apworks.Repositories.DomainRepository, Apworks">
        <constructor>
          <param name="storage">
            <dependency type="Apworks.Events.Storage.IDomainEventStorage, Apworks"/>
          </param>
          <param name="eventBus">
            <dependency type="Apworks.Bus.IEventBus, Apworks"/>
          </param>
        </constructor>
      </register>

      <register type="Apworks.Storage.IStorageMappingResolver, Apworks"
                  mapTo="Apworks.Storage.XmlStorageMappingResolver, Apworks"
                  name="QueryStorageMappingResolver">
        <constructor>
          <param name="fileName" value="QueryObjectStorageMappings.xml"/>
        </constructor>
      </register>

      <register type="Apworks.Queries.Storage.IQueryObjectStorage, Apworks"
                mapTo="Apworks.Queries.Storage.SqlQueryObjectStorage, Apworks">
        <constructor>
          <param name="connectionString"
value="Data Source=.\SQLEXPRESS;Initial Catalog=TinyLibraryQueryDB;Integrated Security=True;Pooling=False;MultipleActiveResultSets=True;"/>
          <param name="mappingResolver">
            <dependency type="Apworks.Storage.IStorageMappingResolver, Apworks" name="QueryStorageMappingResolver"/>
          </param>
        </constructor>
      </register>

    </container>
  </unityConfiguration>

  <system.web>
    <compilation debug="true" targetFramework="4.0" />
  </system.web>
  <system.serviceModel>
    <behaviors>
      <serviceBehaviors>
        <behavior>
          <serviceMetadata httpGetEnabled="true"/>
          <serviceDebug includeExceptionDetailInFaults="false"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
 <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>

</configuration>

以上配置文件主要有两个configSection：apworksConfiguration和unityConfiguration，分别定义了针对Apworks框架和Microsoft Unity的配置内容。以下是Apworks框架配置的部分信息，仅供参考：

• application：指定应用程序的启动器，它将被Apworks.Application.BootStrapperFactory类的Create方法创建
• objectContainer：指定用于Apworks框架的IoC/DI容器适配器，目前Apworks只支持基于Microsoft Unity的适配器
• generators：指定整个系统所使用的标识产生器与序列号产生器。如果未指定针对标识产生器的配置，则系统会默认使用Apworks.Generators.SequentialIdentityGenerator作为标识产生器；如果未指定针对序列号产生器的配置，则系统会默认使用Apworks.Generators.SequentialIdentityGenerator作为序列号产生器
• handlers：指定定义了命令处理器与事件处理器的类型或程序集。当应用程序启动器启动系统的时候，这些处理器将被注册到系统中

注意上面配置节中的黄色高亮部分，记得在实际使用中，将其修改为实际的数据库链接字符串。

至此，我们已经完成了应用系统部分的开发任务，UI部分就是通过调用所需的WCF服务来实现其数据处理功能，因此本系列文章将不再讨论UI部分的实现方式。有兴趣的读者请直接到TinyLibraryCQRS的网站http://tlibcqrs.codeplex.com阅读完整源代码。下一讲将介绍系统的启动与运行相关内容。