[news.eclipse.tools.emf] Re: Attribute dependency validation

[Ed Merks <merks@xxxxxxxxxx>]

José,

Maybe you'd need to create your own cell editor so that you'd be able to know the object holding the property...

http://wiki.eclipse.org/EMF/Recipes#Recipe:_Create_your_own_property_editor_in_a_generated_application

José Parera wrote:

That's right. I've already try it but doesn't solve my problem. I mean, when you change a value in the editor, the associated CellEditor validates the data calling the validateA method. The method, as you point out, validates the data type in an 'out of context' fashion. If I use an object validation constraint I can't call it 'in context' from validateA because I haven't any reference to the object.
So, I can only validate the whole object with all their constraints after the change in the parameter is done. This is not the behavior I wish. If possible, I want to validate the value a priori in order to maintain the model always consistent.

I've been looking at the Validation Framework and I believe the issue is the same since the constraints, even in the 'live' mode, are checked as part of the notifying mechanism after the model change.

In any case I could always validate the object as a result of the parameter change and rollback to the previous value if any violation is found, but this seems to me too involved. If I only could get a reference to the object I could   transform the 'static' definition of the data type to a 'dynamic' one.