Description Marc Schlienger 2011-07-21 08:44:57 EDT

Build Identifier: org.eclipse.emf.mwe.core_1.1.0.v201106070424

Usually a component has the possibility to check its configuration and to perform specific tasks during the call to checkConfiguration. To say it differently, checkConfiguration has side effects, without saying that it is a good thing or a bad thing.

But...

due to the fact that "checkConfiguration()" is not called on the "elseComp" component of ConditionalComponent, some critical initialization might be missing.

I would suggest to override checkConfiguration in ConditionalComponent, with something like this:

	@Override
	public void checkConfiguration(Issues issues) throws ConfigurationException {
		super.checkConfiguration(issues);
		
		// Do not forget to check the config on the elseComp
		if (elseComp != null) {
			elseComp.checkConfiguration(issues);
		}
	}


Reproducible: Always