In WebSocketMessagingAutoConfiguration,
JacksonWebSocketMessageConverterConfiguration is conditioned on
JsonMapper.class, but its constructor requires a JsonMapper bean.
The other nested configuration in the same file,
SpringBootWebSocketMessageBrokerConfiguration, already guards the same
dependency with @ConditionalOnBean(JsonMapper.class).
Similar patterns exist in other modules for mapper-dependent configurations,
for example:
CodecsAutoConfigurationJacksonHttpMessageConvertersConfigurationRSocketStrategiesAutoConfiguration
In practice, I realize this is unlikely to affect normal Boot usage since
JacksonAutoConfiguration will usually provide a JsonMapper bean when the
class is present.
I was wondering if this configuration should back off when the bean is absent,
so that its condition more closely matches its constructor dependency.
In
WebSocketMessagingAutoConfiguration,JacksonWebSocketMessageConverterConfigurationis conditioned onJsonMapper.class, but its constructor requires aJsonMapperbean.The other nested configuration in the same file,
SpringBootWebSocketMessageBrokerConfiguration, already guards the samedependency with
@ConditionalOnBean(JsonMapper.class).Similar patterns exist in other modules for mapper-dependent configurations,
for example:
CodecsAutoConfigurationJacksonHttpMessageConvertersConfigurationRSocketStrategiesAutoConfigurationIn practice, I realize this is unlikely to affect normal Boot usage since
JacksonAutoConfigurationwill usually provide aJsonMapperbean when theclass is present.
I was wondering if this configuration should back off when the bean is absent,
so that its condition more closely matches its constructor dependency.