Very interesting view point Óscar!
In principle we can have both idioms:
1. make requirement to annotate everything (@Action/@Property/@Collection) the new default in v2.0
2. we then add a configuration option to provide a list of classes or packages or regex expressions to activate v1.x behavior for a specific set of classes (making @Action/@Property/@Collection optional for just these)
True its more work for us implementing this with the framework, but if both idioms are still required, it seems worth the effort.
On 2019/12/04 12:20:57, Óscar Bou Bou <[EMAIL PROTECTED]> wrote: