Spring Circuitbreaker fallback not working with JDK (interface based) proxies about resilience4j HOT 3 OPEN

Thank you.
Have you been able to debug it?
There seems to be a difference between using cglib or JDK proxies.
Why do you plan to use JDK proxies? I think Spring Boot sets the default proxy to cglib.

from resilience4j.

Yes, I've been able to debug the issue, the problem is caused by how the fallback method determines the target when using JDK Proxies, the java Method.invoke throws the exception because the proxy object used as the target is not of the correct type.

In R4J version 2.0.2, this was not an issue because there were no proxies involved at all.

Based on the spring documentation for version 6.1.3, it mentions that Spring AOP defaults to using standard JDK dynamic proxies for AOP proxies(https://docs.spring.io/spring-framework/reference/core/aop/introduction-proxies.html) but based on my experience, Spring generally defaults to a CGlib based proxy.

The reason why we use JDK proxies is because we use Spring's WebServiceGatewaySupport to consume soap services and it doesn't work with CGlib proxies, To get the circuitbreakers working on it we had to use JDK proxies.

from resilience4j.

I've make a PR to try solve this problem.

from resilience4j.