Taking into account the @Priority annotation when registering context providers

[Sgitario]

At the moment, users can register multiple context providers for handing the same class by using:

Client client = QuarkusRestClientBuilder.newBuilder()
                    .baseUri(URI.create(uri))
                    .register(MyLowPriorityContextProvider.class)
                    .register(MyHighPriorityContextProvider.class)
                    .build(Client.class);

When doing this, REST Client Reactive will always return the first registered context provider for the matching type:

@Priority(2)
    public static class MyLowPriorityContextProvider implements ContextResolver<Person> {

        @Override
        public Person getContext(Class<?> aClass) {
// ...
        }
    }

    @Priority(1)
    public static class MyHighPriorityContextProvider implements ContextResolver<Person> {

        @Override
        public Person getContext(Class<?> aClass) {
// ...
        }
    }

With these changes, the @Priority annotation is taking into account to return the correct context provider regardless to when it has been registered.

[geoand]

Are you sure that the a larger number means higher priority? In JAX-RS, it's usually the other way around (unless we are talking about @Provider classes on the write path).

Perhaps we should make a check with quarkus-rest-client and see how it behaves?

[Sgitario]

Are you sure that the a larger number means higher priority? In JAX-RS, it's usually the other way around (unless we are talking about @Provider classes on the write path).

Perhaps we should make a check with quarkus-rest-client and see how it behaves?

You're right! Thanks for spotting.

[geoand]

🙏🏼

[Sgitario]

PR updated

[quarkus-bot]

Failing Jobs - Building a96d221

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 19

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 Windows #

- Failing: integration-tests/mongodb-panache 

📦 integration-tests/mongodb-panache

✖ io.quarkus.it.mongodb.panache.reactive.ReactiveMongodbPanacheResourceTest.testMoreRepositoryFunctionalities line 351 - More details - Source on GitHub

java.lang.AssertionError: 
1 expectation failed.
Expected status code <200> but was <500>.

[Sgitario]

The failures are unrelated to these changes.