Custom Extension Registration Changed in Quarkus 3.x

[rdifrango]

I'm creating share modules that used the @Provider to register the features. In particular this is a ContainerRequestFilter and ContainerResponseFilter that was implemented.

The registration of the module was handled by creating a file called javax.ws.rs.ext.Providers and listed the components in it.

For example the code is:

package com.testing.quarkus.filter

@Provider
public class LoggingFilter implements ContainerRequestFilter, ContainerResponseFilter {
 // Code implemented here
}

and javax.ws.rs.ext.Providers is place in module-name/quarkus/runtime/src/main/resources/META-INF/services

com.testing.quarkus.filter.LoggingFilter

But it seems as if with Quarkus 3 this no longer works as LoggingFilter isn't being registered thus not executed and failing my integration tests.

I've tried the following, neither of which seemed to resolve the failed registration:

1. Renaming the file to jakarta.ws.rs.ext.Provider
2. added a build item as follows as shown below

@BuildStep
    AdditionalBeanBuildItem loggingFilter() {
        return AdditionalBeanBuildItem.builder()
                .addBeanClasses(LoggingFilter.class)
                .setDefaultScope(DotNames.SINGLETON)
                .setUnremovable()
                .build();
    }

Any thoughts on what I could be missing?

[rdifrango]

Sigh, I answered my own question, jakarta.ws.rs.ext.Provider needs to be jakarta.ws.rs.ext.Providers see the subtle s on the end.