RESTEasy Classic - annotation on abstract jakarta.ws.rs.core.Application class is not ignored

[rsvoboda]

Describe the bug

RESTEasy Classic - annotation on abstract jakarta.ws.rs.core.Application class is not ignored

#41465 should ensure abstract jakarta.ws.rs.core.Application classes are ignored

But it's not the case when I put @ApplicationPath on it. Path gets unfortunately reflected.
E.g. endpoint is available on http://localhost:8080/rest/hello instead of http://localhost:8080/hello.

Expected behavior

Annotation on abstract jakarta.ws.rs.core.Application class is ignored

Actual behavior

annotation on abstract jakarta.ws.rs.core.Application class is NOT ignored

How to Reproduce?

• Get app https://code.quarkus.io/?e=resteasy&extension-search=resteasy%20classic
• add AbstractApplication into the app
• run mvn clear verify
• alternatively run mvn quarkus:dev and access http://localhost:8080/rest/hello and http://localhost:8080/hello

package org.acme;

import jakarta.ws.rs.ApplicationPath;
import jakarta.ws.rs.core.Application;

@ApplicationPath("/rest")
public abstract class AbstractApplication extends Application {
}

Output of uname -a or ver

macOS

Output of java -version

Java 21

Quarkus version or git rev

Quarkus 3.14.1

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[gsmet]

I don't think it has anything to do with Quarkus. I also am not sure it's a bug.

You would have to check the spec and if it had to be changed, I would expect the change to be in RESTEasy itself?

[rsvoboda]

@geoand did https://github.com/quarkusio/quarkus/pull/41465/files to ignore abstract jakarta.ws.rs.core.Application classes. So that's why I assume annotation on such abstract classes should not make any impact to the app.

Quarkus REST ignores @ApplicationPath in the same use-cese.

@jamezp what's your view on this?

[jamezp]

The annotation is not set as @Inherited. I don't really know how Quarkus scans for types though. Does Quarkus do it's own scanning for applications? I know that's how it works in WildFly, the deployment is scanned for Applications there. RESTEasy doesn't actually scan for the Application.

[geoand]

Same for Quarkus

[jamezp]

Cool, kind of what I assumed :) So it's likely somewhere in Quarkus it needs to be fixed then.

[geoand]

Okay, no I see what the problem is.

@jamezp just to clarify, on WildFly if a class like

package org.acme;

import jakarta.ws.rs.ApplicationPath;
import jakarta.ws.rs.core.Application;

@ApplicationPath("/rest")
public abstract class AbstractApplication extends Application {
}

exists, then @ApplicationPath("/rest") will be completely ignored, correct?

[geoand]

#44195 is what I have in mind

[jamezp]

@geoand Correct. Any abstract classes are simply ignored. TBH I can't think of a use-case for an abstract application class though.