Bump major version number. Our change to the MappingGeneratorImpl might introduce subtle differences when using @JsonbTypeSerializer The old implementation in some edge cases did create corrupt JSON. The main difference is that the JsonbTypeSerializer os only handling the content whereas before it was rendering the full attribute (embedding on top level of the json tree instead of sub-tree)
"test" as Java Object should result in a String "\"test\"". Because the quotes are part of the JSON notation of a string. This is nothing we may 'enforce' - this is clearly requrested by the JSON RFC. And the JSON-B Spec points to the RFC.
class support for serializer/deserializer, partial support for adapters (only write side cause read one is quite challenging) + enforceQuoteString option in case we encounter a jsonb/need conflict
JOHNZON-43 adding encoding as parameter to builder + using utf8 by default in mapper + adding johnzon.mapper.encoding system property for external config
