To play devil's advocate and argue against my own point, it is somewhat
telling that at least two members of the Bean Validation EG maintain
separate object transformation-related libraries. ;) Still, I have a hard
time envisioning what a related specification would look like, regardless
of under which EG's umbrella it was done.
On Mon, Jul 15, 2013 at 11:00 AM, Edward Burns <edward.burns(a)oracle.com>wrote:
>>>>> On Mon, 15 Jul 2013 09:30:36 +0200, Gunnar
GM> I also think a dedicated spec would make sense, but it should be made
GM> that BV and such a new spec work nicely together.
Here my long experience with JCP prompts me to say that in this case,
the domain of conversion is close enough to validation as to make it
worthwhile to keep in BV.
Don't forget, we already have so many specs that it's a job even for me
to keep up, let alone someone who doesn't get paid full time to do so.
At Oracle at least, the oversight for creating a new JSR sets a rather
beanvalidation-dev mailing list