In addition to the flexibility you receive by having error processors run at the web domain level, you may also set filters as to what exception a error processor will handle. For example, perhaps you only want to save exceptions, email only on a SqlException, but have someone paged on all OutOfMemory exceptions.

Configuring this feature couldn't possibly be simple: you just register exceptions as initialization parameters. Here's an example configuration:

<themelia.web>

  <webDomains>

    <add name="sales" path="sales">

      <processors>

        <add type="SavingErrorProcessor">

          <parameters>

            <add value="ArgumentNullException" />

            <add value="CustomException" />

          </parameters>

        </add>

      </processors>

      <factories>

        <add type="ABCCorp.Web.Processing.ProcessorFactory, ABCCorp. Web" />

      </factories>

    </add>

    <add name="sales" path="sales">

      <processors>

        <add type="EmailSendingErrorProcessor">

          <parameters>

            <add value="OutOfMemoryException" />

          </parameters>

        </add>n

      </processors>

    </add>

  </webDomains>

</themelia.web>

In this example, only exceptions of OutOfMemoryException will be emailed and then only for the sales web domain. Most exceptions in the System, System.Data, System.Web, and System.Xml assemblies have been aliased in Themelia Pro.