Andrew Guibert

thanks for pointing this out @brunoabdon, it does indeed look like a bug in the javadoc

Part of #168

> backward compatible: a currently working app creating programmatically instances would get a new encoding, adapter etc if not which breaks apps, even simple config as formatting does. How does...

current configuration would only be overridden *if* environments happen to specify the _exact_ `jsonb.*` property names we choose, which is very unlikely and therefore we should not be concerned with...

Perhaps we can wait and see what the naming convention is for Jakarta Config properties. If we are concerned with the property names colliding, we could qualify them such as:...

> Ok, take an app working doing some custom build of jsonb instances, add mp support, redeploy, it is broken cause your explicit config is overriden. If not enough for...

I think this is a good idea and we should work on this for 2.0. Seems like a duplicate of #88 though, do you agree @m0mus?

I think the first bullet point is pretty much the same as #88 `Extend JsonbConfig functionality to cover all functionality provided by @JsonbXXX annotations` The second bullet point is the...

having a parent issue is fine -- I've raised #172 and linked it to this issue

Links for the existing approaches mentioned in the OP: GSON: https://static.javadoc.io/com.google.code.gson/gson/2.6.2/com/google/gson/reflect/TypeToken.html Jackson: https://fasterxml.github.io/jackson-core/javadoc/2.2.0/com/fasterxml/jackson/core/type/TypeReference.html