Tatu Saloranta

Hmmh. `Converter`s are really problematic since question then is whether decision should be based on original or converted type. But my initial thinking is that no converter should be used...

Wrong repo: `GenericJackson2JsonRedisSerializer` is not part of Jackson so this needs to be filed somewhere else.

As I recall, the fundamental problem in case like this is that the name should be based on field name, and not on extracting it from getter or setter: latter...

Records do not follow Bean convention anyway, due to no set-/get-prefixes. And no need to modify capitalization.

So, `AccessorNamingStrategy` is a public extension point, but only meant for application developers (sort of end user), not for modules and so on. And not by jackson-databind itself (it shouldn't...

I don't think that changing default behavior (either with or without `USE_STD_BEAN_NAMING`) is something we can do for 2.x. I _thought_ USE_STD_BEAN_NAMING would lower-case all leading upper-case; and non-USE_STD_BEAN_NAMING just...

Oh. And looking at `MapperFeature.USE_STD_BEAN_NAMING`; case of "getURL()" * When enabled -> `"URL"` (and hence) * When disabled -> `"url"` so it won't do what would work here, `"Url"`. But...

Not 100% sure what would be expected here: custom `AccessorNamingStrategy` can be used to make things work as expected (to some degree at least); but I don't see how to...

Correct, all use of `StringBuffer` is accidental/historical left-over: nothing in core parser/generator is thread-safe (minus some of `SymbolTable` reuse which is explicitly synchronized as necessary) -- they are not meant...

Whoa! That sounds more like a bug indeed: unless some comment explicitly states otherwise, and I don't there is. So it should be shift-right to get +50% increase.