You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customizing an existing ClientResources instance is difficult for integration libraries as it requires a BeanPostProcessor calling ClientResources.mutate(). Using BeanPostProcessor limits the ability of what Spring Beans can be injected during customization.
This came up while trying to set Lettuce's ClientResources.tracing(…) using a Spring Cloud Sleuth bean. It would be good to have a ClientResourcesBuilderCustomizer API to let Spring Boot create DefaultClientResources while being able to hook into builder customization.
The text was updated successfully, but these errors were encountered:
Customizing an existing
ClientResources
instance is difficult for integration libraries as it requires aBeanPostProcessor
callingClientResources.mutate()
. UsingBeanPostProcessor
limits the ability of what Spring Beans can be injected during customization.This came up while trying to set Lettuce's
ClientResources.tracing(…)
using a Spring Cloud Sleuth bean. It would be good to have aClientResourcesBuilderCustomizer
API to let Spring Boot createDefaultClientResources
while being able to hook into builder customization.The text was updated successfully, but these errors were encountered: