[news.eclipse.tools.emf] Re: DataBinding + Validation Framework

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

[...]

>> I'm also thinking it may prove easier to work with a
>> ValidationStatusProvider rather than an IValidator.  For instance,
>> UpdateValueStrategy works with and afterGet, afterConvert, and
>> beforeSet validator, but doesn't have the notion (as far as I can
>> tell) of an afterSet/model level validator.  ValidationStatusProvider
>> (see MultiValidator for an example) looks like the way to handle
>> validation once the target->model update has finished.
> It will be interesting to see what Tom thinks about support for
> validation.  It seems an important issue...
>>
>>

I have to admit that this something I didn't deal today directly in
databinding but I do the validation when the users wants to save the
changes.

There's an interesting JSR 303 which deals with validation and there's a
request to implement such support for Eclipse-Databinding [1].

Maybe it is a good time to get together and think about how we should
implement the stuff in Eclipse-Databinding so that people can easily
plug in their own model validation (like people can plug in currently
their property validation).

Though the question is whether such a model validation should happen
really at the databinding level which works at the level of model
properties and not a complete model graph. Does this make sense?

>> I'll follow up if I make any more progress.
> Thanks Will!

Please do so :-)

>>
>> -Will
>>

[1]https://bugs.eclipse.org/bugs/show_bug.cgi?id=279166