Register server exception mapper method of the Rest-Interface implementation class

[andrejpetras]

Motivation:
We generate server endpoints for our Rest-Interfaces from openapi.yaml files. Generator generates interfaces, and we need to write only the implementation classes. We do have multiple versions (v1, v2, ...) of rest interface (multiple openapi.yaml files) in one application. We would like to have a custom server exception mapper for each version, which will create a valid response to the corresponding version.

Closes: #36872

[geoand]

Thanks for this.

Can you add a test that covers the use case you have in mind?

[andrejpetras]

@geoand I added my test case to the PR

[geoand]

Thanks!

[quarkus-bot]

✔️ 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.

[andrejpetras]

@geoand Could we select this for version 3.5.1 as well?

[geoand]

I am a little hesitant to do that honestly.

[andrejpetras]

@geoand I totally understand.

I am not sure if the current workaround (duplicate the @Path annotation also on implementation class) have any side-effects on running application.

I can only see the warning logs when starting the applications

[WARNING] [io.smallrye.openapi.runtime.scanner.spi] SROAP07903: Duplicate operationId: getPortalByUrl produced by Class:
 io.github.onecx.portal.rs.external.v1.controllers.PortalRestController, Method: jakarta.ws.rs.core.Response 
getPortalByUrl(java.lang.String url) and Class: gen.io.github.onecx.portal.rs.external.v1.PortalV1Api, Method: 
jakarta.ws.rs.core.Response getPortalByUrl(java.lang.String url)

Do you see a problem with the workaround?

[geoand]

It should be just fine

[andrejpetras]

@geoand thx, I'll stick with it and wait for 3.6.0.

[geoand]

👌🏼