Seems like the right way to go to me.
On Wednesday, 20 May 2020 01:29:54 UTC+2, Tatu Saloranta wrote: > > So, a bug was reported as: > > https://github.com/FasterXML/jackson-databind/issues/2729 > > which is related to problems in Jackson scala module 2.10 handling > auto-detection, and uncovering what seems like a small but significant > deviation from Bean Naming: Jackson not requiring that the first > character following "get" and "set" prefix is upper-case, to > auto-detect getter/setter. > > So: Jackson will detect accessors like > > public int getxxx() { ... } > public void set_value(int x) { .... } > > which are probably not compatible with Bean Naming as originally defined. > > My first thought was that this is more a feature than bug, since I > suspect there are users expecting this behavior. > As such, a change should be by adding a new `MapperFeature` to allow > opt-in, defaulting to using old logic for 2.x (but change in 3.0) > > But then I remembered that there is already > `MapperFeature.USE_STD_BEAN_NAMING` that could be used here too. > > WDYT? I seem to be oscillating between two states here, and wanted to > hear how others feel about proposed change. > > -+ Tatu +- > -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to jackson-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/019e1c33-5b46-4516-8b72-703ebcbc9c0bo%40googlegroups.com.
