Thomas Segismont

@ebadta81 the second issue can be worked around by avoiding a schema reference: ```yaml paths: /upload/image: post: summary: image upload operationId: upload-image tags: - upload requestBody: required: true content: "multipart/form-data":...

The PR shall also update the doc to indicate content type can be specified in the spec file

Tracked down the difference to be in this method: https://github.com/vert-x3/vertx-web/blob/135879f8400d0d69a82100c0e63b5def9a03bfed/vertx-web-openapi/src/main/java/io/vertx/ext/web/openapi/impl/MultipartFormBodyProcessorGenerator.java#L73-L85 When the multipart form schema is a reference, this method is not useful because the schema has been already loaded...

Sure

@jponge what's the process for upgrading? Do you have any idea how long it takes?

Can you rather share source code please? Thank you

@vietj this looks like a good addition to me, wdyt? @pmlopes on the user group you commented that perhaps this should be considered together with reworking the `blockingHandler` method from...

@pmlopes I think we could make it work with a coroutine handler. But does this mean every handler created by this router instance would then becoming, for example in case...

The chain idea sounds better to me: it's aligned with the Vert.x Web programming style. I guess the `withCoroutineFactory` name is just for example's sake, right? In practice it would...

Thank you @InfoSec812 @vietj Given this is not a blocker, I believe it is fine to postpone to `4.2.1`.