Bug 294739 [EAS] need service for reporting errors and warnings to the user (in a dialog, or through logging)
Rationale: Having them separated is quite risky, because it introduces artificial division, in which errors are handled. Probably UI plug-ins will use IStatusHandler and Logger, while core plug-ins will just log. How can we notify the user that something went completely wrong in headless plug-in? We need to create a bridge, so actually merge those two frameworks. On the other hand, why should we pass the same problem to IStatusHandler & to Logger? Are there any Statuses which should be shown to the user (and interrupt his work) but should not be logged?
bundles/org.eclipse.e4.ui.workbench.swt/src/org/eclipse/e4/ui/workbench/swt/internal/PartRenderingEngine.java
for (Class<?> intf : interfaces) {
			Activator.trace(Policy.DEBUG_CONTEXTS,
					"Adding " + intf.getName() + " for " 
							+ contextModel.getClass().getName(), null);
			context.set(intf.getName(), contextModel);
			populateModelInterfaces(contextModel, context, intf.getInterfaces());
		}
	}
	public Object createGui(MUIElement element, Object parent) {
		if (!element.isToBeRendered())
			return null;
		if (element instanceof MContext) {
			MContext ctxt = (MContext) element;
			
			
			if (ctxt.getContext() == null) {
				IEclipseContext parentContext = element.getParent() == null ? appContext
						: getContext(element.getParent());
				IEclipseContextStrategy strategy;
				if (element instanceof MContribution) {
					IContributionFactory contributionFactory = (IContributionFactory) parentContext
							.get(IContributionFactory.class.getName());
					MContribution contribution = (MContribution) element;
					Bundle bundle = contributionFactory.getBundle(contribution
							.getURI());
					strategy = new BundleContextStrategy(bundle);
				} else {
					strategy = null;
				}
				IEclipseContext lclContext = EclipseContextFactory.create(