<routingExtension> of <serviceBehavior>

Article
02/24/2011

Provides run-time access to the routing service to allow dynamic modification of the routing configuration.

Schema Hierarchy

<system.serviceModel>
  <behaviors>
    <serviceBehaviors>
      <behavior> of <serviceBehaviors>
        <routingExtension> of <serviceBehavior>

Syntax

<behaviors>  <serviceBehaviors>    <behavior name=String">      <routingExtension filterTable=”String”         routeOnHeadersOnly="Boolean"         SoapProcessingEnabled=”Boolean” />    </behavior>  </serviceBehaviors></behaviors>

Attributes and Elements

The following sections describe attributes, child elements, and parent elements.

Attributes

Attribute	Description
filterTable	A string that specifies the name of the routing table that contains filters to be evaluated by the routing service. This value must match the name attribute of a <filterTable> element in the <filterTables> section.
routeOnHeaderOnly	A Boolean value that specifies whether the filter will examine both the message body and the header, or the header only. The default is true.
soapProcessingEnabled	A Boolean value that specifies whether SOAP processing should occur.

Child Elements

None.

Parent Elements

Element	Description
<behavior> of <endpointBehaviors>	Specifies a behavior element.

Remarks

When added to the service’s behavior configuration, this configuration element enables routing for the service. You can specify the actual routing table to be used by the service in this element.

Using this configuration section, you can change your routing settings on the fly when your deployment pattern changes. At runtime, you can register your own routing extension with new routing settings and the routing service will begin using the updated configuration information for new messages and sessions, while leaving in-flight messages/sessions using whatever rules were in place when they started. This gives you the ability to do session-safe, recycle-less reconfiguration of the Routing Service during runtime.