is the bug you mentioned with the ObservablesManager gone by now (3.6 release)? How would the code look like without your workaround?
cheers, Daniel

I meanwhile found out that a MultiValidator seems to be the way to go.
However I can not get it running. The examples of “org.eclipse.jface.examples.databinding.snippets” are working but if I use my EMFObservables the validate-method is never called. Are there any known bugs or so ?

I did:
bindingContext.addValidationStatusProvider(new MyMultiValidator(…

and as far as I understood the validate method should then be called whenever any of the observables accessed by MyMultiValidator are modified.

MyMultiValidator uses just a single EMF observable:
private final IObservableValue myEMFObservable;

which is created in the constructor:
myEMFObservable = EMFObservables.observeValue(myModel, myModelPackage.Literals.VALUE);

I have created a binding between an edit field and its corresponding model feature.

Now I have the problem that the validator check depends on the value of another feature and therefore the check must not only be executed when the corresponding model feature changes but also when the other feature changes. What is the recommended way to implement this behaviour?

Thanks in advance,

chris

I already tried before what you suggested.
However I meanwhile got it running finally.
The problem had a completely different cause.
It seems that I did not check out the CVS resource properly before. I still do not know what was wrong but I re-checked out and now it just works.

I have another short question:
I would like to bind an edit field to a single value of a multi-valued feature. The index of the value to bind is known when binding. Is there an easy way to do that or do have to create a custom control and make it updatable myself ?

Is there an example anywhere for this?

Thanks again,

chris