Paulo Lopes

@wapsa if we call the `onException` handler, does it still make sense to throw after anyway?

Your findings are correct, I've commented on the linked PR. Yes the naming is "terrible", I wanted to preserve the API but the behavior is not really consistent with the...

In the new openapi router, we have fixed this by only having 1 way to do this.

@DemonicTutor mutipart form is handled by `vertx-core` as it delegates to netty to do the parsing

Maybe @slinkydeveloper can help as he knows best that code.

This one is more complicated as htdigest may require a digest of the full body response, which we don't cache

@jponge maybe you can help using the `gradle-vertx-plugin` ?

@vietj Is this needed? as we're not releasing `vertx-lang-js` anymore?

I'd assigned @slinkydeveloper as he's the OpenAPI expert :wink:

Extra helpers could be added. Like in the example above, we could have a helper just for passing the `auth-token` as: ```java service = new MicroServiceVertxEBProxy(vertx, MicroService.ADDRESS); service .execute() .authorizeAndCall(ctx.user().get("id_token"))...