PropertiesWebClientHttpServiceGroupConfigurer#getOrder() still returns Ordered.HIGHEST_PRECEDENCE, while the RestClient sibling was changed to Ordered.HIGHEST_PRECEDENCE + 10 in 72eaeec for gh-48296.
This leaves WebClient-backed HTTP service groups with the limitation that gh-48296 fixed for RestClient. A WebClientHttpServiceGroupConfigurer ordered at, say, Ordered.HIGHEST_PRECEDENCE + 5 cannot supply an initial WebClient.Builder through InitializingClientCallback. The properties configurer runs first, creates the default builder through the ClientCallback variant of forEachClient, and the initializing callback then fails with "Client builder already initialized".
If this is considered a bug, would it be okay for me to submit a small PR?
PropertiesWebClientHttpServiceGroupConfigurer#getOrder()still returnsOrdered.HIGHEST_PRECEDENCE, while the RestClient sibling was changed toOrdered.HIGHEST_PRECEDENCE + 10in 72eaeec for gh-48296.This leaves WebClient-backed HTTP service groups with the limitation that gh-48296 fixed for RestClient. A
WebClientHttpServiceGroupConfigurerordered at, say,Ordered.HIGHEST_PRECEDENCE + 5cannot supply an initialWebClient.BuilderthroughInitializingClientCallback. The properties configurer runs first, creates the default builder through theClientCallbackvariant offorEachClient, and the initializing callback then fails with "Client builder already initialized".If this is considered a bug, would it be okay for me to submit a small PR?