Christoph Strobl

Thanks for the heads up on this one, seems to have slipped through for quite a while. The `WriteResultChecking` dates back to the early days of the project when writes...

Update - there's a PR (spring-projects/spring-framework#30396) targeting FW 6.1 timeframe.

I might be missing something here. A fresh boot `3.0.5` project with the above entity works just fine on `openjdk version "17.0.4.1"`. Maybe you can take the time to provide...

@vikas-singh-maersk do you have a [minimal sample](https://stackoverflow.com/help/minimal-reproducible-example) (something that we can unzip or git clone, build, and deploy) that reproduces the problem at hand?

@christophe-michard thanks for the reproducer!

I need to revisit `StoreConversions` and the flagging for `java.time` types which may take some time. Meanwhile there's always the option of adding `--add-opens=java.base/java.time=ALL-UNNAMED`.

@christophe-michard you may also want to try it this way: ```java MongoMappingContext mappingContext = new MongoMappingContext(); MappingMongoConverter mappingMongoConverter = new MappingMongoConverter(new DefaultDbRefResolver(mongoDbFactory), mappingContext); mappingContext.setSimpleTypeHolder(mappingMongoConverter.getCustomConversions().getSimpleTypeHolder()); mappingContext.afterPropertiesSet(); mappingMongoConverter.afterPropertiesSet(); ```

The issue is scheduled for triage in the team. Please be patient and give us a little time. Thank you!

Good catch - thanks for reporting! We'll take care of this.

Thanks for pointing this out. I need to revisit the XML config section to see if changes done to the `ConnectionStringPropertyEditor` need to be reflected there. The MongoDB connection string...