anchor.diff:  
   |Option |Default |Description
   
  -|`scope` |`Route` |A scope for either *`Route`* or *`Context`* which defines if the current
  +|`scope` |`Route` |A scope for either `Route` or `Context` which defines if the current
   number of inflight exchanges is context based or for that particular
   route.
   
  
positive.code: </route>
  ---------------------------------------------------------
  
  == Configuring Policy Sets
  
  *`RoutePolicy`* has been further improved to allow addition of policy
  sets or a collection of policies that are concurrently applied on a
  route. The addition of policies is done as follows.
  
  In the example below, the route *`testRoute`* has a *`startPolicy`*
  and *`throttlePolicy`* applied concurrently. Both policies are applied
  as necessary on the route.
  
  [source,xml]
  ----------------------------------------------------------------------------------------------
  <bean id="date" class="org.apache.camel.routepolicy.quartz.SimpleDate"/>
  
  <bean id="startPolicy" class="org.apache.camel.routepolicy.quartz.SimpleScheduledRoutePolicy">
    <property name="routeStartDate" ref="date"/>
    <property name="routeStartRepeatCount" value="1"/>
    <property name="routeStartRepeatInterval" value="3000"/>        
  </bean>
  
  <bean id="throttlePolicy" class="org.apache.camel.impl.ThrottlingInflightRoutePolicy">
    <property name="maxInflightExchanges" value="10"/>        
  </bean>
  
  <camelContext id="testRouteContext" xmlns="http://camel.apache.org/schema/spring">
    <route id="testRoute" autoStartup="false" routePolicyRef="startPolicy, throttlePolicy">
      <from uri="seda:foo?concurrentConsumers=20"/>
      <to uri="mock:result"/>
    </route>
  </camelContext>
  ----------------------------------------------------------------------------------------------
  
  == Using `RoutePolicyFactory`
  
  If you want to use a route policy for every route, you can use
  a *`org.apache.camel.spi.RoutePolicyFactory`* as a factory for creating
  a *`RoutePolicy`* instance for each route. This can be used when you
  want to use the same kind of route policy for every routes. Then you
  need to only configure the factory once, and every route created will
  have the policy assigned.
  
  There is API on CamelContext to add a factory, as shown below
  
  [source,java]
  ----------------------------------------------------------
  context.addRoutePolicyFactory(new MyRoutePolicyFactory());
  ----------------------------------------------------------
  
  And from XML DSL you just define a *`<bean>`* with the factory
  
  [source,xml]
  ----------------------------------------------------------------------
  <bean id="myRoutePolicyFactory" class="com.foo.MyRoutePolicyFactory"/>
  ----------------------------------------------------------------------
  
  The factory has a single method that creates the route policy
  
  [source,java]
  ------------------------------------------------------------------------------------------------------------------------
  /**
   * Creates a new {@link org.apache.camel.spi.RoutePolicy} which will be assigned to the given route.
   *
   * @param camelContext the camel context
   * @param routeId      the route id
   * @param route        the route definition
   * @return the created {@link org.apache.camel.spi.RoutePolicy}, or <tt>null</tt> to not use a policy for this route
   */
  RoutePolicy createRoutePolicy(CamelContext camelContext, String routeId, RouteDefinition route);
  ------------------------------------------------------------------------------------------------------------------------
  
  Note you can have as many route policy factories as you want. Just call
  the *`addRoutePolicyFactory`* again, or declare the other factories
  as *`<bean>`* in XML.
  
  
negative.code: route if the current number of inflight exchanges is higher than this
  value.
  
  |`resumePercentOfMax` |`70` |A percentage `0..100` which defines when the throttling should resume
  again in case it has been suspended.
  
  |`loggingLevel` |`INFO` |The logging level used for logging the throttling activity.
  