Custom serializers/deserializers defined via annotations get overridden by Afterburner

Question

Custom serializers/deserializers defined via annotations get overridden by Afterburner

Closed this issue 12 years ago · 1 comments

Currently Afterburner will happily optimize all kinds of serializers/deserializers for primitive types (and Strings).
This should not occur when there are serializer/deserializer overrides that use annotations.

Answer 1 · 2012-07-30T16:41:28.000Z

Added checks, matching unit tests: now (de)serializers indicated with annotations should be honored, meaning they are not overridden by Afterburner (also means they can't be optimized).