Bug 342998 Refactor ESelectionService into multiple classes
While there is a master/slave relationship "enforced" by the current implementation, it is non-obvious as the code is quite convoluted. The implementation needs to be refactored to enhance readability.
tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/application/ESelectionServiceTest.java
partService.activate(partB);
		assertNull(listener.getPart());
		assertNull(listener.getSelection());
	}
	public void testSelectionListener3() {
		MApplication application = ApplicationFactoryImpl.eINSTANCE
				.createApplication();
		MWindow window = BasicFactoryImpl.eINSTANCE.createWindow();
		application.getChildren().add(window);
		application.setSelectedElement(window);
		MPart partA = BasicFactoryImpl.eINSTANCE.createPart();
		partA.setElementId("partA"); 
		window.getChildren().add(partA);
		window.setSelectedElement(partA);
		MPart partB = BasicFactoryImpl.eINSTANCE.createPart();
		partB.setElementId("partB"); 
		window.getChildren().add(partB);
		initialize(applicationContext, application);
		getEngine().createGui(window);
		IEclipseContext contextA = partA.getContext();
		IEclipseContext windowContext = window.getContext();
		ESelectionService serviceA = (ESelectionService) contextA
				.get(ESelectionService.class.getName());
		ESelectionService windowService = (ESelectionService) windowContext
				.get(ESelectionService.class.getName());
		EPartService partService = (EPartService) windowContext
				.get(EPartService.class.getName());
		Object selectionA = new Object();
		Object selectionB = new Object();
		SelectionListener listener = new SelectionListener();