@PreSerialize / @PostDeserialize method annotations

[Lilianne-Blaze]

Could you please consider something like @PreSerialize and @PostDeserialize method annotations?
It would be very useful for data sanitization, security/completeness checks, logging, "condensing" data (having "dense" fields used only in storage/transfer, compressed from "real" not-serializable fields before serialization and decompressed after deserialization). I know most or all of that can be done in custom serializers/deserializers, but with pre-serialize/post-deserialize methods it would be much easier both to write and maintain later.

[cowtowncoder]

@Lilianne-Blaze Idea has floated around for a while, and there might be an older issue for suggestion.
No concrete plans, although since we are slowly working towards 3.0, this would be good time to think of both exactly how API should work and how implementation may be added with minimal (ideally non-measurable) performance impact on cases where not pre-/post-processor is used.

This could belong under jackson-future-ideas, but being relatively concrete and familiar idea it's probably fine to have it here as RFE.