On Mon, 21-Nov-2016 17:40, Gunnar Morling wrote:
Agreed that it can be made work for all cases (the RI does it already
or less). Question is whether by supporting e.g. Optional fields we
encourage modelling styles that are discouraged by the JDK team. But maybe
that's just a question of documentation/wording, i.e. we could support it
everywhere but only show usage on return values / getter props in the spec.
I think I would also vote for making it possible for the sake of consistency.
If your argument about minimising/preventing "misuse" would hold, one would
need to look at supporting date types without timezone information again.
There the argument was also that a user should not be prevented to use Bean
Validation constraints and documentation is enough to make the user aware of