spring aot compile doesnot process jedis-HostandPort class which cause below exception when packaging can somebody tell me how to fix about spring-aot-smoke-tests

[wilkinsona]

You appear to be trying to bind configuration properties directly to redis.clients.jedis.HostAndPort. That won't work in a native image as the class has not been compiled with -parameters. Rather than binding directly to HostAndPort you should bind properties to a class that you control and can compile with -parameters. An instance of HostAndPort can then be created from the instance of your own class.

If you have any further questions, please follow up on Stack Overflow or Gitter. We prefer to use GitHub issues only for bugs and enhancements.

[sintoku921]

You appear to be trying to bind configuration properties directly to redis.clients.jedis.HostAndPort. That won't work in a native image as the class has not been compiled with -parameters. Rather than binding directly to HostAndPort you should bind properties to a class that you control and can compile with -parameters. An instance of HostAndPort can then be created from the instance of your own class.

If you have any further questions, please follow up on Stack Overflow or Gitter. We prefer to use GitHub issues only for bugs and enhancements.

do you mean i create a sub class as extends HostandPort class ,and try to compile ? thks and i will try and get a response

[sintoku921]

i have used a dataClass init configuration for jedis config insteadof use HostAndPort class directly,like below ,but the exeception still ouucred while native compiling .

@ConfigurationProperties(prefix = "jedis")
@Data
public class RedisConfigProperties {
   
    // host list
    private List<RedisHost> hosts = new ArrayList<>();

    @Data
    public static class RedisHost{
        private String host;
        private int port;
    }
    
    public Set<HostAndPort> getRedisHosts(){
        return new HashSet<>(U.map(hosts, o -> new HostAndPort(o.getHost(), o.getPort())));
    }
}

[scottfrederick]

As Andy stated above:

If you have any further questions, please follow up on Stack Overflow or Gitter. We prefer to use GitHub issues only for bugs and enhancements.

Please post your question as suggested, with as much detail and sample code as possible so that the community can try to help you.