I have a vert.x app running on 4.5.11 and I am creating an Openshift client using fabric libraries. The vertx http factory creates a new vert.x object in the vertx http client factory in the kubernetes vertx httpclient. How can I pass the vertx instance to it so that it doesn’t create a new vert.x instance.

I have an API that mostly produces and consumes an application/vnd mime type.

I have an api that mosly produces and consumes a application/vnd. mime type.
For some endpoints I also want to handle different mime type.
How do I avoid specyfing the produces() and consumes() for every route?

I’m trying to implement a thread-per-request design using Vert.x Web’s HTTP server. When I run the following code, I am not able to process any more requests until response.done() is called:

I am revently learning vert.x. But cann’t understand how to setup user registration and login/logout system by vert.x. Can anyone help me understand?

is there a way to use the localstorage-function of a browser using vert.x?

Our OAuth2 Server has the possibility to handle OpenTelemetry TraceId. Is there a way to inject a traceID into the VertX OAuth2 Handler?