@RegisterForProxy not working for rest-client interface

[phillwatson]

I have a Rest Client interface:

@Produces(MediaType.APPLICATION_JSON)
@RegisterForReflection
public interface OpenIdTokenApi {
    @POST
    @Consumes(MediaType.APPLICATION_JSON)
    public TokenExchangeResponse exchangeToken(TokenExchangeRequest request);

    ...
}

I create the proxy for this using the @Produces annotation and a qualifier (the qualifier identifies the source of the base URL) :

    protected OpenIdTokenApi openIdRestApi(OpenIdConfigResponse openIdConfig) {
        log.debug("Creating OpenId REST API [url: {}]", openIdConfig.tokenEndpoint);

        URI baseUri = URI.create(openIdConfig.tokenEndpoint);
        return RestClientBuilder.newBuilder()
            .baseUri(baseUri)
            .build(OpenIdTokenApi.class);
    }

    @Produces
    @ApplicationScoped
    @NamedAuthProvider(AuthProvider.GOOGLE)
    public OpenIdTokenApi googleRestApi(@NamedAuthProvider(AuthProvider.GOOGLE) OpenIdConfigResponse openIdConfig) {
        return openIdRestApi(openIdConfig);
    }

I have successfully used the "DynamicProxyConfigurationFiles" argument.
-Dquarkus.native.additional-build-args=-H:DynamicProxyConfigurationFiles=proxy-config.json

with the following content in the proxy-config.json file:

[
  {
    "interfaces": [
      "com.hillayes.openid.rest.OpenIdTokenApi",
      "org.jboss.resteasy.client.jaxrs.internal.proxy.ResteasyClientProxy"
    ]
  },
  {
    "interfaces": [
      "com.hillayes.openid.rest.OpenIdTokenApi",
      "org.jboss.resteasy.microprofile.client.RestClientProxy",
      "java.io.Closeable"
    ]
  }
]

This file content came about whilst trying to perform a native compilation, and has been working fine. I'm not sure why I need two entries for the same interface, but it won't work without both being present.

I recently came across the @RegisterForProxy annotation and have tried to use it to replace the config file. However, I'm not having much success. I think the reason is the need to provide two proxy-config entries for the same interface.

I place the @RegisterForProxy annotation on the interface and have tried specifying only one of the configs above:

@RegisterForProxy(targets = {
    OpenIdTokenApi.class,
    org.jboss.resteasy.client.jaxrs.internal.proxy.ResteasyClientProxy.class
})

or

@RegisterForProxy(targets = {
    OpenIdTokenApi.class,
    org.jboss.resteasy.microprofile.client.RestClientProxy.class,
    java.io.Closeable.class
})

When I specify one I get a org.graalvm.nativeimage.MissingReflectionRegistrationError about the other being missing.
I've also tried giving both, and even combining them:

@RegisterForProxy(targets = {
    OpenIdTokenApi.class,
    org.jboss.resteasy.client.jaxrs.internal.proxy.ResteasyClientProxy.class,
    org.jboss.resteasy.microprofile.client.RestClientProxy.class,
    java.io.Closeable.class
})

But it still gives the MissingReflectionRegistrationError exception.

I have two questions:

1. Why would I need two proxy config entries for the same interface?
2. How can I register these two proxy configs using the @RegisterForProxy annotation (perhaps an answer to the first question will resolve this)?

[quarkus-bot[bot]]

/cc @cescoffier (rest-client), @geoand (rest-client)

[geoand]

So you are using the quarkus-resteasy-client extension?

[phillwatson]

This is in a sub-module. The pom in that module includes the following dependencies:

        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-client</artifactId>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.jboss.resteasy.microprofile</groupId>
            <artifactId>microprofile-rest-client</artifactId>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.eclipse.microprofile.rest.client</groupId>
            <artifactId>microprofile-rest-client-api</artifactId>
            <scope>provided</scope>
        </dependency>

The pom of the parent module includes the following:

        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-resteasy-client</artifactId>
        </dependency>
        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-resteasy</artifactId>
        </dependency>
        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-resteasy-jackson</artifactId>
        </dependency>

Whenusing the proxy-config.json, it also located in the main/resources/ of the parent module.
And the -H:DynamicProxyConfigurationResources=proxy-config.json is in the pom of the parent module.

[geoand]

I assume that you would pass the class name you are using in proxy-config.json

[phillwatson]

I have used the same names as used in the proxy-config.json. However, the json file has two entries for the same rest interface:

[
  {
    "interfaces": [
      "com.hillayes.openid.rest.OpenIdTokenApi",
      "org.jboss.resteasy.client.jaxrs.internal.proxy.ResteasyClientProxy"
    ]
  },
  {
    "interfaces": [
      "com.hillayes.openid.rest.OpenIdTokenApi",
      "org.jboss.resteasy.microprofile.client.RestClientProxy",
      "java.io.Closeable"
    ]
  }
]

As I say, I'm not sure why it needs two entries, but it won't work, and throws an exception, if I don't specify both.

Similarly, when using @RegisterForProxy, if I only specify one of these target lists, it complains that the other is required, but I can't see how to specify both lists - as is done in the json file.

I really appreciate you taking the time to look at this.

[geoand]

I can't say I have an answer for you unfortunately.

And to be honest, all of our efforts are on the quarkus-rest-client these days

[phillwatson]

Thank you for taking the time anyway. I appreciate it.
I'll continue to use the config json file, for now.

[geoand]

👍🏽