Allow to support inheritance in JAX-RS Resource included via Application#getClasses

[essobedo]

fixes #16754

Motivation

If a JAX-RS Resource inherits a @Path annotation from an interface or a subclass and is included to the JAX-RS Application via the method getClasses, it is actually ignored by the current implementation of a JAX-RS Application in the extension Resteasy Classic.

Modifications:

• Improves the filter allowing to exclude @Path annotations by checking concrete classes when the enclosing class of the annotation is an interface or an abstract class.
• Adds a dedicated test for it

Result

The inheritance of @Path annotations is now supported by the JAX-RS Application in the extension Resteasy Classic.

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 4e282fa

Status	Name	Step	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 15	Build	Test failures	Logs	Raw logs
✖	Native Tests - Security2	Build	Test failures	Logs	Raw logs
✖	Native Tests - Security3	Build	⚠️ Check →	Logs	Raw logs

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 15 #

📦 extensions/oidc-client-filter/deployment

✖ io.quarkus.oidc.client.filter.OidcClientFilterDevModeTest.testGetUserName - More details - Source on GitHub

📦 extensions/oidc/deployment

✖ io.quarkus.oidc.test.CodeFlowDevModeDefaultTenantTestCase.testAccessAndRefreshTokenInjectionDevMode - More details - Source on GitHub

✖ io.quarkus.oidc.test.CodeFlowDevModeTestCase.testAccessAndRefreshTokenInjectionDevMode - More details - Source on GitHub

✖ io.quarkus.oidc.test.SecurityDisabledTestCase. - More details - Source on GitHub

---

⚙️ Native Tests - Security2 #

📦 integration-tests/oidc

✖ io.quarkus.it.keycloak.BearerTokenAuthorizationInGraalITCase.testAccessAdminResourceCustomHeaderNoBearerScheme - More details - Source on GitHub

[essobedo]

Hi @geoand and @stuartwdouglas, WDYT of this PR and its corresponding ticket?

[geoand]

LGTM, thanks!

[essobedo]

@geoand Hi, should I propose a backport for the version 1.13?

[geoand]

Sure, go ahead and add the label.

This should apply cleanly to the 1.13 Branch

[essobedo]

Sure, go ahead and add the label.

This should apply cleanly to the 1.13 Branch

I don't have sufficient rights to add labels but here it is #16823

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 4e282fa

Status	Name	Step	Test failures	Logs	Raw logs
✖	JVM Tests - JDK 11	Build	Test failures	Logs	Raw logs
✖	JVM Tests - JDK 15	Build	Test failures	Logs	Raw logs

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 11 #

📦 extensions/oidc-client-filter/deployment

✖ io.quarkus.oidc.client.filter.OidcClientFilterDevModeTest.testGetUserName - More details - Source on GitHub

📦 extensions/oidc/deployment

✖ io.quarkus.oidc.test.CodeFlowDevModeDefaultTenantTestCase.testAccessAndRefreshTokenInjectionDevMode - More details - Source on GitHub

✖ io.quarkus.oidc.test.CodeFlowDevModeTestCase.testAccessAndRefreshTokenInjectionDevMode - More details - Source on GitHub

✖ io.quarkus.oidc.test.SecurityDisabledTestCase. - More details - Source on GitHub

---

⚙️ JVM Tests - JDK 15 #

📦 extensions/oidc-client-filter/deployment

✖ io.quarkus.oidc.client.filter.OidcClientFilterDevModeTest.testGetUserName - More details - Source on GitHub

📦 extensions/oidc/deployment

✖ io.quarkus.oidc.test.CodeFlowDevModeDefaultTenantTestCase.testAccessAndRefreshTokenInjectionDevMode - More details - Source on GitHub

✖ io.quarkus.oidc.test.CodeFlowDevModeTestCase.testAccessAndRefreshTokenInjectionDevMode - More details - Source on GitHub

✖ io.quarkus.oidc.test.SecurityDisabledTestCase. - More details - Source on GitHub

[essobedo]

FYI The build failures don't seem to be related to this PR

[geoand]

Same comment as #16823 (comment) :)

[essobedo]

Same comment as #16823 (comment) :)

@geoand done too

[essobedo]

This one sounds good now