Skip to:
As discussed on our call today, introduce a setting that allows configuring the following three behaviors for Byte[]/Character[] handling:
Byte[]
Character[]
INVALID(default) - Throw an informative and actionable error if the types are used explicitly in the domain model
INVALID
ALLOW - Do not throw an error, but keep the array semantics proper i.e. allow null elements
ALLOW
LEGACY - Legacy behavior i.e. use ByteArrayJavaType and CharacterArrayJavaType which disallow null elements
LEGACY
ByteArrayJavaType
CharacterArrayJavaType
Document the setting in the migration guide.
As discussed on our call today, introduce a setting that allows configuring the following three behaviors for
Byte[]/Character[]handling:INVALID(default) - Throw an informative and actionable error if the types are used explicitly in the domain modelALLOW- Do not throw an error, but keep the array semantics proper i.e. allow null elementsLEGACY- Legacy behavior i.e. useByteArrayJavaTypeandCharacterArrayJavaTypewhich disallow null elementsDocument the setting in the migration guide.