Bug 265164 Consolidate all interface access under the appropriate context
At the moment the various 'Legacy<xxx>' implementations maintain discreet fields to store a variety of interface implementations (IWorkbench, IWorkbenchWindow, IPartSite...). With the new Context menchanism in place these should be placed in to the context structure at the appropriate location in the context tree and all the access methods (getService, getAdapter and a variety of 'direct' access API's like 'IWorkbecnh#getWorkingSetManager') should use the context to gain access to the API interface.
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/ILegacyHook.java
/*******************************************************************************
 * Copyright (c) 2009 IBM Corporation and others.
 * All rights reserved. This program and the accompanying materials
 * are made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at
 * http://www.eclipse.org/legal/epl-v10.html
 * 
 * Contributors:
 *     IBM Corporation - initial API and implementation
 *******************************************************************************/
package org.eclipse.e4.workbench.ui;
import org.eclipse.e4.ui.model.application.MApplication;
import org.eclipse.e4.ui.model.application.MMenu;
import org.eclipse.e4.ui.model.workbench.MPerspective;
import org.eclipse.e4.ui.model.workbench.MWorkbenchWindow;
import org.eclipse.e4.workbench.ui.internal.Workbench;
public interface ILegacyHook {
	public void init(Workbench e4Workbench, MApplication<MWorkbenchWindow> workbench);
	public void loadMenu(MMenu menuModel);
	public void loadPerspective(MPerspective<?> perspModel);
}