Resteasy reactive - Interfaces are added as a Bean causing jakarta.enterprise.inject.AmbiguousResolutionException

[floresmleonardo]

Describe the bug

When utilizing RESTeasy Reactive, an issue arises when multiple classes implement the same interface and, the interface has methods with the @path annotation. In this scenario, Quarkus mistakenly registers the interface as a bean, which results in a jakarta.enterprise.inject.AmbiguousResolutionException due to the presence of multiple beans without a qualifier.

Note: This issue occurs specifically in the context of RESTeasy Reactive with Quarkus. If you change to RESTeasy Classic, then, it behaves as expected.

Expected behavior

Quarkus should handle the usage of the interface correctly and avoid registering it as a bean to prevent the jakarta.enterprise.inject.AmbiguousResolutionException.

Actual behavior

Quarkus mistakenly treats the interface as a bean, leading to the jakarta.enterprise.inject.AmbiguousResolutionException error.

How to Reproduce?

Repo: https://github.com/floresmleonardo/quarkus-bug-resteasy-reactive

Run the application

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

3.2.0

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

No response

Additional information

No response

[quarkus-bot]

/cc @FroMage (resteasy-reactive), @Sgitario (resteasy-reactive), @geoand (resteasy-reactive), @stuartwdouglas (resteasy-reactive)

[geoand]

Looks like a bug indeed but I fear that addressing this will cause other issues.

In any case, it needs some investigation.

[diogocarleto]

Hi guys, same thing here, I'm trying to migrate to resteasy reactive and the same happens, if I comment the @Path and @GET/@POST it works. I'm using the 2.16.8.Final version.

[geoand]

#34888 fixes the issue