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
It would be great, if RestClient followed the spring.mvc.converters.preferred-json-mapper=gson setting or had a similar own. Now it only checks the classpath for the existence of jackson classes (in DefaultRestClientBuilder.initMessageConverters()). Since my application includes spring-boot-starter-actuator jackson will always be on the classpath, so there is no way RestClient will create GsonHttpMessageConverter instead of MappingJackson2HttpMessageConverter. As a workaround we can pass HttpMessageConverters from application context to RestClient.Builder, but DefaultRestClientBuilder.initMessageConverters() creates more converters, than I have in context. It seems, I don't need them, but I haven't tested it properly.
The text was updated successfully, but these errors were encountered:
It would be great, if RestClient followed the
spring.mvc.converters.preferred-json-mapper=gson
setting or had a similar own. Now it only checks the classpath for the existence of jackson classes (inDefaultRestClientBuilder.initMessageConverters()
). Since my application includesspring-boot-starter-actuator
jackson will always be on the classpath, so there is no way RestClient will createGsonHttpMessageConverter
instead ofMappingJackson2HttpMessageConverter
. As a workaround we can passHttpMessageConverter
s from application context toRestClient.Builder
, butDefaultRestClientBuilder.initMessageConverters()
creates more converters, than I have in context. It seems, I don't need them, but I haven't tested it properly.The text was updated successfully, but these errors were encountered: