anchor.diff:  configure using a servlet you use the init-param as shown above. When
   configuring directly in the rest-dsl, you use the appropriate method,
   such as `enableCORS`, `host,contextPath`, dsl. The options
  -with `api.xxx` is configured using `apiProperty` dsl.
  +with `api.xxx` are configured using `apiProperty` dsl.
   
   [width="100%",cols="10%,10%,80%",options="header",]
   |===
   |Option |Type |Description
   
   |cors |Boolean |Whether to enable CORS. Notice this only enables CORS for the api
  -browser, and not the actual access to the REST services. Is default
  +browser and not the actual access to the REST services. Is default
   false.
   
   |swagger.version |String |Swagger spec version. Is default 2.0.
  
positive.code: 
  |apiContextIdListing |boolean |Whether to allow listing all the CamelContext names in the JVM that has
  REST services. When enabled then the root path of the api-doc will list
  all the contexts. When disabled then no context ids is listed and the
  root path of the api-doc lists the current CamelContext. Is default
  false.
  
  |apiContextIdPattern |String |A pattern that allows to filter which CamelContext names is shown in the
  context listing. The pattern is using regular expression and * as
  wildcard. Its the same pattern matching as used by
  Intercept
  |===
  
  
negative.code:     .consumes("application/json").produces("application/json")
  ----
  
  Here we have set up two security definitions
  
  - OAuth2 - with implicit authorization with the provided url
  - Api Key - using an api key that comes from HTTP header named _myHeader_
  