Allow @JsonAnySetter on Creator constructors

[JooHyukKim]

resolves #562

[cowtowncoder]

Alas, this is not acceptable from performance perspective: all annotation introspection must occur when constructing deserializers and related handlers. It should be possible to change handling to keep track of information about existence of "any setter", instead of trying to introspect for every deserialization call.

[cowtowncoder]

Impressive. I am bit hesitant to consider this as one more thing before work on Property Introspection rewrite, but no harm in figuring out how this could work. Added some notes.

[JooHyukKim]

Impressive. I am bit hesitant to consider this as one more thing before work on Property Introspection rewrite,

I concur. And also in the issue #562, this feature is to get included in 3.x.

So I think we can safely consider this feature only after Property Introspection rewrite.

but no harm in figuring out how this could work. Added some notes.

Thankssss! I will keep them updated

[JooHyukKim]

WDYT, @cowtowncoder ?
We can visit #4396 after this.

[cowtowncoder]

WDYT, @cowtowncoder ? We can visit #4396 after this.

Ok. I am still struggling with this; reading again. It is improving, but I am still worried about added complexity. But at the same time this IS a VERY highly voted feature (that is, #562 is)

So it'd be great to be able to somehow simplify handling. Not sure how to, tho, so I need to keep on re-reading code.

Aside from that, some missing things:

1. No tests yet for Record case? (should work fine I assume, but just noting)
2. Only supports Map-backed any-setter, but not JsonNode-backed one (unlike Field-based one) -- adding support is probably not hard but does add to code, special casing

[JooHyukKim]

So it'd be great to be able to somehow simplify handling. Not sure how to, tho, so I need to keep on re-reading code.

I totally agree. Current implementation is both complex and scattered around places.
I sort of focused on making work, not so much around maintainability.

I will probably start isolating the any-setter logics first, maybe to a class, then will read through your comments and add suggested missing parts.

thnx @cowtowncoder

PS: Reviews applied first.

[JooHyukKim]

Temporarily closing this in favor of #4558 where I added record and JsonNode tests
/cc @cowtowncoder