Bug 354402

Description Stephan Herrmann 2011-08-10 11:57:09 EDT

In a project that uses both a JavaValidator and a validator written in Check
I found that the former is skipped if the latter reports any errors for
the current model. This also affects the dependent validators
ImportUriValidator and NamesAreUniqueValidator.

Digging into the code I was surprised to see lines like this in all three 
validate methods of CompositeEValidator:

	result = result && val.getDelegate().validate(eClass, eObject, diagnostics, context);

Is "&&" really intended here? I would expect:

	boolean success = val.getDelegate().validate(eClass, eObject, diagnostics, context);
	result = result && success;