Tatu Saloranta

What @pjfanning show is THE recommended way to do configuration. I am 100% against change to serialize Numbers (BigInteger or otherwise) as JSON Strings and consider it unlikely default will...

On deprecation of `JsonGenerator.Feature.WRITE_BIGDECIMAL_AS_PLAIN` -- while this will not be removed from 2.x ever, there is replacement (since this is format-agnostic setting): StreamWriteFeature.WRITE_BIGDECIMAL_AS_PLAIN using which removed deprecation warnings. And since...

Ah. It is possible `JsonGenerator.Feature.WRITE_BIGDECIMAL_AS_PLAIN` not yet marked as deprecated. But it will be removed from 3.0, whereas `StreamWriteFeature` counterpart remains.

I am not 100% sure if this is doable or not: but I don't thing `@JsonUnwrapped` will work to achieve that. On figuring out working mapping: the usual way of...

So, yes, I can see why logically supporting `@JsonUnwrapped` for `List`s on serialization side could make sense for XML. Unfortunately `jackson-databind` is supposed to be format-agnostic (although there are some...

I think that overriding of `SerializerFactory` is very rare thing, this is probably the first time I've heard users doing that. So I don't think the problem here was anticipated....

Ah ok. Yes, we should make it possible to configure `SerializerFactory` even with XML module. Right now I am bit overloaded with Jackson work so I may not have time...

Ah. Yes, flow of configuration gets bit hairy, since `SerializerFactory` is amongst oldest extant abstractions and its configuration was not as well-thought-out as newer additions. This does explain the problem...

I did #680 and I think it might be the best small thing I can do; will merge.

Correct, I cannot think of an obvious easy solution unfortunately. This issue has come up a few times, and in hindsight I wish I had added a `MapperFeature` to allow...