anchor.diff:  </user>
   ----
   
  +=== Body content example (JSON)
  +
   [source, json]
  -.Body content example (json)
   ----
   {
       "id": "{#request.paths[3]}",
  
positive.code: 
  == Description
  
  Mock policy is providing you with the ability to create mocked response when a consumer is calling one of your services.
  This way, you do not have to provide a functional backend and it gives you more time to think about your API contract.
  
  You can think this policy as a contract-first approach since you are able to create a fully-functional API without the
  need to write any line of code to handle consumer calls.
  
  Internally, this policy replace the default HTTP invoker by putting a mock invoker. There is no more HTTP call between
  the gateway and a remote service / backend.
  
  When defining response body content, you can use the internal Expression Language to provide a dynamic mock.
  
  [source, xml]
  .Body content example (xml)
  ----
  <user id="{#request.paths[3]}">
      <firstname>{#properties['firstname_' + #request.paths[3]]}</firstname>
  
negative.code: }
  ----
  
  == Configuration
  
  You can configure the policy with the following options:
  
  |===
  |Property |Required |Description |Type |Default
  