Failling fast is not really an option since it is the correct behavior and
does not violate java contract.
We can tune some config like the extsing readAttributeBeforeWrite to reuse
it to read your map and enrich it instead of overwriting it but it can also
lead to inconsistent values when reusing
Thanks for the explanation Romain.
In this case I have been able to remove the final modifiers from the
affected fields. This was the simplest thing to do as the mapping was being
done automatically in REST API calls rather than explicitly via Johnzon.
The problem did take some tracking down. I c
Hi Dave,
yes this is tracked in https://issues.apache.org/jira/browse/JOHNZON-142
and 77
long story short setting final fields was not intended and lead to
inconsistencies so this behavior has been dropped.
if you need the previous behavior and are sure it is intended you can get
it back using:
Hi,
I am attempting to upgrade from TomEE 7.0.4 (Johnzon 1.0.0) to TomEE 7.1.0
(Johnzon 1.0.1) and have encountered a change in behaviour with JSON
deserialization. The below test passes with Johnzon 1.0.0 but fails with
1.0.1.
Tracing this through with the different Johnzon versions it appears t
