Date: July 3, 2009 11:58:46 CEDT
Subject: [jsr-303-eg] Make payload optional
I was talking to Mike Keith from Oracle the other day and he became concerned at us adding more and more mandatory attributes to constraint definitions.
He was proposing to make the payload attribute optional. In other words, custom annotations would not have to add this property, though the spec would recommend it and all built-in annotations would have it.
The idea is to keep life easy for constraint developers.
I am sympathetic to the idea, anybody fiercely against?
PS: Mike was also arguing for making groups optional but I am more reluctant on that, groups has become an important mechanism in BV, so I would keep that mandatory. Thoughts?