Afterburner: #174 handle primitive/string property with ser

[BOFA1ex]

link #174
Using serializer to handle it like ObjectFieldPropertyWriter/ObjectMethodPropertyWriter

[cowtowncoder]

Um, no. What problem is this supposed to fix? It adds overhead and seems against the idea of avoiding unnecessary checks. Optimized BeanPropertyWriters should only be assigned when there is only the Jackson standard implementation and we can fully optimize handling.

Under what conditions would this change be needed?

I'd at least need to see a test of something that does not work without change presented.

[cowtowncoder]

Um, no. What problem is this intended to fix? It adds overhead and seems against the idea of avoiding unnecessary checks. Optimized BeanPropertyWriters should only be assigned when there is only the Jackson standard implementation and we can fully optimize handling.

Under what conditions would this change be needed?

I'd at least need to see a test of something that does not work without change presented.

[BOFA1ex]

Before afterburner using SerializerModifier to change BeanPropertyWriter, there have another modifier to assign serializer in it. and then the serializer is declare with @JacksonStdImpl, it will skip the check (SerializerUtil.isDefaultSerializer(bpw.getSerializer()).

But primitive/string method writer do nothing after access#getValue just gen.writeString(value).
if not declare with @JacksonStdImpl, it using reflect not asm, so why did i try to append AfterBurnerModule to improve pref.