How to make quarkus-smallrye-openapi return correct response schema for vertx?

[rainmanhhh]

Please use StackOverflow for questions.

This helps the community to be able to find answers to their similar issues more easily.

Click this link to ask on StackOverflow with the "quarkus" tag.

if I use io.quarkus.vertx.web.Route:

    @Route(methods = [HttpMethod.GET])
    fun hello(rc: RoutingContext) {
        rc.response().end("hello")
    }

localhost:8080/swagger-ui report "No operations defined in spec!"

[quarkusbot]

/cc @EricWittmann

[rainmanhhh]

I found that with resteasy api(@get @path) and jdk8 CompletionStage, openapi works fine. Will it be a performance bottleneck using resteasy http handler instead of vertx.web?

[EricWittmann]

@phillip-kruger I think we may have another scanner type candidate - vert.x annotations.

[phillip-kruger]

@EricWittmann cool ! Just not sure if we can assume all @Route is REST Endpoints ?

[rainmanhhh]

jax-rs annotations is a little bit troublesome(although it's a jsr standard). If you're planning to replace it, what about using openapi annotations instead? (and implement the routing logic with vertx)

[EricWittmann]

@EricWittmann cool ! Just not sure if we can assume all @Route is REST Endpoints ?

No but maybe the scanner can check the methods? I don't really know enough about vert.x to be able to say. But I do know that we have a lot of vert.x experts around. :)

[phillip-kruger]

I think we need to create a issue in smallrye for this, with some use case examples on how this will work. I.e when do we treat something as a REST endpoint and when not. @rainmanhhh w.d.y.t ?