-
Notifications
You must be signed in to change notification settings - Fork 192
Exposing ObjectMapper disables Spring Boot JacksonAutoConfiguration #1209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
seems that removing the @bean from couchbaseObjectMapper() would fix this. |
Yes, is there any particular reason why we needed |
The @bean is to expose the objectMapper. Is there some other way to do that? I suppose a user could override the couchbaseObjectMapper() in their Config class as follows, but this looks really ugly. static ObjectMapper theObjectMapper; @OverRide ObjectMapper couchbaseObjectMapper(){
The purpose of exposing the ObjectMapper was to allow it to be customized. |
Overriding couchbaseObjectMapper() is definitely better than exposing bean. The couchbaseObjectMapper() is only called once right? There is no need to use static property. |
Right. Not sure what I was thinking. @OverRide ObjectMapper couchbaseObjectMapper(){ |
Exposing ObjectMapper used by JsonSerializer implemented here: #1132, disables Spring Boot JacksonAutoConfiguration#jacksonObjectMapper(), since it is annotated with
@ConditionalOnMissingBean
.It forces usage of Couchbase ObjectMapper Bean which disables Spring Boot Jackson customizations (properties, modules, ...).
The text was updated successfully, but these errors were encountered: