Bug 321995 Application-Context should hold Display-Realm
The application context should hold the databinding realm for the current SWT-Display it can then be used to by code to synchronize with the UI-Thread in a widget-toolkit agnostic way.
bundles/org.eclipse.e4.ui.workbench.swt/src/org/eclipse/e4/ui/internal/workbench/swt/E4Application.java
}
	}
	public void saveModel() {
		try {
			handler.save();
		} catch (IOException e) {
			
			e.printStackTrace();
		}
	}
	public E4Workbench createE4Workbench(IApplicationContext applicationContext) {
		args = (String[]) applicationContext.getArguments().get(
				IApplicationContext.APPLICATION_ARGS);
		IEclipseContext appContext = createDefaultContext();
		appContext.set(IApplicationContext.class, applicationContext);
		
		if (!appContext
				.containsKey("org.eclipse.e4.ui.workbench.modeling.EModelService")) {
			throw new IllegalStateException(
					"Core services not available. Please make sure that a declarative service implementation (such as the bundle 'org.eclipse.equinox.ds') is available!");
		}
		
		IContributionFactory factory = (IContributionFactory) appContext
				.get(IContributionFactory.class.getName());
		
		
		String lifeCycleURI = getArgValue(E4Workbench.LIFE_CYCLE_URI_ARG,
				applicationContext, false);
		if (lifeCycleURI != null) {
			lcManager = factory.create(lifeCycleURI, appContext);