Allow the use of @Blocking on @ClientExceptionMapper

[geoand]

• Relates to: @Blocking Annotation on "entrypoint" in subclass not detected #38275 (comment)

[cescoffier]

I believe none of the other extension handling @Blocking handle this case.

@ozangunalp do you know about reactive messaging?
@alesj do you know about gRPC?
@mkouba do you know about websocket next?

[geoand]

That's a very good point, however the REST client might be unique in that the various Providers are run on the event loop by default (which was probably a mistake)

[mkouba]

@mkouba do you know about websocket next?

@cescoffier if you ask whether we produce an ExecutionModelAnnotationsAllowedBuildItem for endpoint callbacks then yes, we do: https://github.com/quarkusio/quarkus/blob/main/extensions/websockets-next/deployment/src/main/java/io/quarkus/websockets/next/deployment/WebSocketProcessor.java#L135-L145 :D

[ozangunalp]

For messaging, we only detect incoming/outgoing annotated methods on beans and not from superclasses.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 9b72af5.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[alesj]

@cescoffier is gRPC exception handler is a plain ServerCall.Listener impl, which I guess could work with blocking, if there is a @Blocking before on the method

[cescoffier]

Ok, so, messaging and gRPC - only for the concrete method. WS and REST: super-method too.

We may need to make this a bit more homogenous (BTW does @Blocking has the inherent meta-annotation?)

[mkouba]

Ok, so, messaging and gRPC - only for the concrete method. WS and REST: super-method too.

Hm, I'm not quite following. WS Next does not support class-level @Blocking/@NonBlocking atm.

We may need to make this a bit more homogenous (BTW does @Blocking has the inherent meta-annotation?)

Keep in mind that @Inherited should only be considered for class-level annotations. And no, neither @Blocking nor @NonBlocking is annotated with @Inherited.