anchor.diff:  ----
   <dependency>
     <groupId>io.vertx</groupId>
  -  <artifactId>vertx-openapi</artifactId>
  +  <artifactId>vertx-web-openapi</artifactId>
     <version>${maven.version}</version>
   </dependency>
   ----
  
positive.code: Vert.x OpenAPI mounts the correct {@link io.vertx.ext.web.validation.ValidationHandler} for you, so you can access to request parameters and request body.
  Refer to https://vertx.io/docs/vertx-web-validation/java/[Vert.x Web Validation documentation] to learn how to get request parameters & request body and how to manage validation failures
  
  === Define security handlers
  
  A security handler is defined by a combination of schema name and scope. You can mount only one security handler for a combination.
  For example:
  
  [source,$lang]
  ----
  {@link examples.OpenAPI3Examples#addSecurityHandler}
  ----
  
  You can use included Vert.x security handlers, for example:
  
  [source,$lang]
  ----
  {@link examples.OpenAPI3Examples#addJWT}
  ----
  
  When you generate the {@link io.vertx.ext.web.Router} the router factory fails if there is a missing security handler.
  
  For debugging/testing purpose you can disable this check with {@link io.vertx.ext.web.openapi.RouterFactoryOptions#setRequireSecurityHandlers(boolean)}
  
  === Not Implemented Error
  
  Router Factory automatically mounts a default handler for operations without a specified handler.
  This default handler fails the routing context with 405 `Method Not Allowed`/501 `Not Implemented` error.
  You can enable/disable it with {@link io.vertx.ext.web.openapi.RouterFactoryOptions#setMountNotImplementedHandler}
  and you can customize this error handling with {@link io.vertx.ext.web.Router#errorHandler}
  
  === Response Content Type Handler
  
  Router Factory automatically mounts a {@link io.vertx.ext.web.handler.ResponseContentTypeHandler} handler when contract requires it.
  You can disable this feature with {@link io.vertx.ext.web.openapi.RouterFactoryOptions#setMountResponseContentTypeHandler}
  
  === Operation model
  
  If you need to access to your operation model while handling the request,
  you can configure the router factory to push it inside the `RoutingContext` with {@link io.vertx.ext.web.openapi.RouterFactoryOptions#setOperationModelKey(String)}:
  
negative.code: {@link examples.OpenAPI3Examples#setOptions}
  ----
  
  == Access to operations
  
  To access to an https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md#operationObject[Operation] defined in contract, use {@link io.vertx.ext.web.openapi.RouterFactory#operation(String)}.
  This method returns an {@link io.vertx.ext.web.openapi.Operation} instance that you can use to both access the model and assign handlers
  