There probably is interest, as there are cases where this would be
beneficial, but I am not aware of anyone working on this.
There are couple of aspects to runtime introspection; in particular
annotation access (typically "one-time" overhead for inspecting all
annotations to figure out settings for (de)serializers), and then
actual property set/get via reflection.
Afterburner does second case, dynamically (so after usual annotation
introspection dynamic accessors and constructor callers are
generated).
I suspect both cases could be covered, possibly separately. First case
(annotation access) alternative could, for example, be exposed via
different `AnnotationIntrospector` feeding settings, and could be
useful for reducing start-up overhead on serverless platforms,
and Android (where annotation access is hideously slow for some reason).
Second case (generating accessors) can be addressed in many ways as
well; some tools generate source code to compile (and I think this is
nowadays more common one, and probably easier). Extending Afterburner
could theoretically work, but one problem is that Afterburner uses
standard reflection access as fallback where needed, and this is
probably not something that would be practical if all reflection
access was to be replaced.
-+ Tatu +-