anchor.diff:  To use an address forwarder, you must first configure a connector to the remote AMQP server for the address space. For more information about address space connectors, see link:{BookUrlBase}{BaseProductVersion}{BookNameUrl}#ref-address-space-example-connectors-messaging[Address space connector examples].
   
   Address forwarding is supported only in the `standard` address space type, and only for the `queue` and `subscription` address types. With the `queue` address type, you can forward messages to a remote AMQP server or from a remote AMQP server to a local queue. With the `subscription` address type, you can create a forwarder to a remote AMQP address, but you cannot create a forwarder that copies messages to the subscription. That is, the `subscription` address type supports forwarding in the `out` direction only, as shown in the example.
  +
  +For outgoing forwarders, you can assign a `priority` value to the consumer associated with the forwarder. This allows you to influence message routing within the AMQP network by favoring one link over another. If the forwarder has
  +a lower priority than other consumers, messages will only flow through the forwarder when the other consumers do not have credit or cannot accept a message for other reasons (for example, message selectors). The value must be an integral number in the range
  +-2^31 to 2^31-1.  Values lower than zero reduce the forwarder's priority relative to other consumers, while values greater than zero raise it.  If the priority is unassigned, a default value of 0 is used.
   
   In the following examples, it is assumed that a connector, `remote1`, has been configured for the address space.
   
  
positive.code: <1> (Required) Specifies the name of the forwarder, which is used to ensure a unique identity.
  <2> (Required) Specifies the remote address to forward messages to. The address must be prefixed with the connector name and must be identical to the address matching patterns defined on the connector.
  <3> (Required) Specifies the direction of message flow, which is either `out` or `in`. A value of `out` forwards messages to the remote endpoint. A value of `in` forwards messages from the remote endpoint.
  
  
negative.code:   - name: f1 <1>
      remoteAddress: remote1/clients/me/1 <2>
      direction: out <3>
      priority: 10 <4>
  
  ----
  <1> (Required) Specifies the name of the forwarder, which is used to ensure a unique identity.
  <2> (Required) Specifies the remote address to forward messages to. The address must be prefixed with the connector name and must be identical to the address matching patterns defined on the connector.
  <3> (Required) Specifies the direction of message flow, which is either `out` or `in`. A value of `out` forwards messages to the remote endpoint. A value of `in` forwards messages from the remote endpoint.
  <4> (Optional) Specifies the priority assigned to the consumer used by the forwarder (integral number in the range -2^31 to 2^31-1 with a default of 0).  Applies to outgoing forwarders only.
  
  == Forwarding messages from a remote AMQP server to a local queue
  
  In this example, you receive messages from an address `prices/milk` on a remote AMQP server.  The messages are then moved to a local queue, `myqueue`.
  
  [source,yaml,options="nowrap"]
  ----
  