These are chat archives for spring-cloud/spring-cloud
InheritanceAwareMethodArgumentResolverWrappersimply walks up the method override hierarchy to find the parameter definition that actually carries the annotation. You could probably tweak the
BeanPostProcessorto only wrap resolvers that extend
RequestParamMethodArgumentResolver... its implementation is a bit more complicated than the others
spring.cloud.config.name(from memory) (which can be different to
EurekaDiscoveryClientand post-processing the original
EurekaDiscoveryClient @Bean, replacing with the subclass (necessary because the original bean is not conditional). Then I repeated the process for ribbon by extending
DomainExtractingServerListand returning from my Ribbon configuration.
staticbut I had wondered whether that would pose potential problems for multiple Feign contexts/JVM. Is there any other obvious Spring-specific possibility of which I am just not aware?
ThreadLocalto make available the initializing context?