Tatu Saloranta

There are fairly significant problems in implementing sorting: "parent" serializer has no visibility into unwrapped properties. Fixing that fundamental problem is something I hoped to do for 3.0 but never...

@impwang91 If you can upgrade to `2.20.x` (2.20.1), could try enabling `MapperFeature.FIX_FIELD_NAME_UPPER_CASE_PREFIX` which has a good chance of solving your issue (see #5152 for details if interested).

Will leave open for now but likely close soon since solution/work-arounds exists and there seems to be no issue to fix.

Ok. So, it might be possible to write some comments through `JsonNode` by using "raw value" (and at streaming level, `JsonGenerator.writeRaw()` (NOT "rawValue" actually)) but that is definitely cumbersome. But...

Unfortunately I don't thing add-on interfaces help a lot with the core issue (or maybe I just don't see it). Support would still need to be added in `JsonNode` implementations....

FWTW, Jackson 2.6 actually does support injection of default values for Creator properties. Default value is defined as value that matching `JsonDeserializer` method `getNullValue(DeserializationContext ctxt)` returns. I have also ensured...

I think we'd first need an issue explaining what is the problem to fix.

Ok, use of `LinkedHashMap` in itself is acceptable, retaining order possibly useful, with modest (probably non-measurable) overhead. But adding overhead of reordering for every use is not good -- many...

> > But adding overhead of reordering for every use is not good -- many users would get penalized despite not caring about ordering. > > You mean the recursion?...

> The only change I made there was replacing iteration with recursion. Hmh. Ok, I probably need to re-read PR. But yes, recursion on its own can also be problematic...