RR treat providers from class path differently than REST Easy classic

[michalvavrik]

Describe the bug

Our test is declaring multiple MessageBodyWriters and also has org.jboss.resteasy:resteasy-multipart-provider as dependency (as we have another tests for multipart stuff). Once #27981 got merged, test HttpAdvancedReactiveIT#testMediaTypePassedToMessageBodyWriter started to fail https://github.com/quarkus-qe/quarkus-test-suite/actions/runs/3068463481/jobs/4960620155 . I mentioned same behavior works for REST Easy classic while same providers (newly 48 providers, pff ) are also registered there (I checked). I think it's down to https://jakarta.ee/specifications/restful-ws/3.1/jakarta-restful-ws-spec-3.1.html#provider_priorities that says Application-supplied providers enable developers to extend and customize the JAX-RS runtime. Therefore, an application-supplied provider MUST always be preferred over a pre-packaged one if a single one is required.

Expected behavior

RR behaves same as classic one - ApplicationJsonSerializer defined by our app is used.

Actual behavior

org.jboss.resteasy.plugins.providers.StringTextStar is preferred over ones provided in our application

How to Reproduce?

Reproducer:

Steps to reproduce the behavior:

1. git clone https://github.com/michalvavrik/rr-msg-body-write-reproducer
2. mvn clean install

Output of uname -a or ver

Linux fedora 5.19.6-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Aug 31 17:58:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Output of java -version

openjdk version "17.0.3" 2022-04-19

GraalVM version (if different from Java)

GraalVM CE 22.1.0

Quarkus version or git rev

999-SNAPSHOT

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

Apache Maven 3.8.6

Additional information

No response