anchor.diff:  }
   ----
   
  -Also, you don't have to take care about the _Content-Type_ header since Mock policy is able to detect automatically the
  -content type.
  -
   == Configuration
   
  -You can configure the policy with the following options :
  +You can configure the policy with the following options:
   
   |===
   |Property |Required |Description |Type |Default
  
positive.code: 
  |===
  
  
  [source, json]
  .Configuration example
  ----
  "mock": {
      "status": "200",
  
negative.code: 
  == Description
  
  You can use the `mock` policy to create mock responses when a consumer calls one of your services.
  This means you do not have to provide a functional backend as soon as you create your API, giving you more time to think about your API contract.
  
  You can think of the policy as a contract-first approach -- you are able to create a fully-functional API without needing to write a single line of code to handle consumer calls.
  
  Internally, this policy replaces the default HTTP invoker with a mock invoker. There are no more HTTP calls between
  the gateway and a remote service or backend.
  
  When defining the response body content, you can use Expression Language to provide a dynamic mock response.
  
  == Examples
  
  Note that you don't need to provide the `Content-Type` header, since the Mock policy can automatically detect the
  content type.
  
  === Body content example (XML)
  
  [source, xml]
  ----
  <user id="{#request.paths[3]}">
      <firstname>{#properties['firstname_' + #request.paths[3]]}</firstname>
  