All Downloads are FREE. Search and download functionalities are using the official Maven repository.

org.eclipse.core.resources.ISaveParticipant Maven / Gradle / Ivy

Go to download

AspectJ tools most notably contains the AspectJ compiler (AJC). AJC applies aspects to Java classes during compilation, fully replacing Javac for plain Java classes and also compiling native AspectJ or annotation-based @AspectJ syntax. Furthermore, AJC can weave aspects into existing class files in a post-compile binary weaving step. This library is a superset of AspectJ weaver and hence also of AspectJ runtime.

There is a newer version: 1.9.22.1
Show newest version
/*******************************************************************************
 *  Copyright (c) 2000, 2009 IBM Corporation and others.
 *
 *  This program and the accompanying materials
 *  are made available under the terms of the Eclipse Public License 2.0
 *  which accompanies this distribution, and is available at
 *  https://www.eclipse.org/legal/epl-2.0/
 *
 *  SPDX-License-Identifier: EPL-2.0
 *
 *  Contributors:
 *     IBM Corporation - initial API and implementation
 *******************************************************************************/
package org.eclipse.core.resources;

import java.util.EventListener;
import org.eclipse.core.runtime.CoreException;

/**
 * A participant in the saving of the workspace.
 * 

* Plug-ins implement this interface and register to participate * in workspace save operations. *

*

* Clients may implement this interface. *

* @see IWorkspace#save(boolean, org.eclipse.core.runtime.IProgressMonitor) */ public interface ISaveParticipant extends EventListener { /** * Tells this participant that the workspace save operation is now * complete and it is free to go about its normal business. * Exceptions are not expected to be thrown at this point, so they * should be handled internally. *

* Note: This method is called by the platform; it is not intended * to be called directly by clients. *

* * @param context the save context object */ void doneSaving(ISaveContext context); /** * Tells this participant that the workspace is about to be * saved. In preparation, the participant is expected to suspend * its normal operation until further notice. saving * will be next, followed by either doneSaving * or rollback depending on whether the workspace * save was successful. *

* Note: This method is called by the platform; it is not intended * to be called directly by clients. *

* * @param context the save context object * @exception CoreException if this method fails to snapshot * the state of this workspace */ void prepareToSave(ISaveContext context) throws CoreException; /** * Tells this participant to rollback its important state. * The context's previous state number indicates what it was prior * to the failed save. * Exceptions are not expected to be thrown at this point, so they * should be handled internally. *

* Note: This method is called by the platform; it is not intended * to be called directly by clients. *

* * @param context the save context object * @see ISaveContext#getPreviousSaveNumber() */ void rollback(ISaveContext context); /** * Tells this participant to save its important state because * the workspace is being saved, as described in the supplied * save context. *

* Note: This method is called by the platform; it is not intended * to be called directly by clients. *

*

* The basic contract for this method is the same for full saves, * snapshots and project saves: the participant must absolutely guarantee that any * important user data it has gathered will not be irrecoverably lost * in the event of a crash. The only difference is in the space-time * tradeoffs that the participant should make.

*
    *
  • Full saves: the participant is * encouraged to save additional non-essential information that will aid * it in retaining user state and configuration information and quickly getting * back in sync with the state of the platform at a later point. *
  • *
  • Snapshots: the participant is discouraged from saving non-essential * information that could be recomputed in the unlikely event of a crash. * This lifecycle event will happen often and participant actions should take * an absolute minimum of time. *
  • *
  • Project saves: the participant should only save project related data. * It is discouraged from saving non-essential information that could be recomputed * in the unlikely event of a crash. *
  • *
* For instance, the Java IDE gathers various user preferences and would want to * make sure that the current settings are safe and sound after a * save (if not saved immediately). * The Java IDE would likely save computed image builder state on full saves, * because this would allow the Java IDE to be restarted later and not * have to recompile the world at that time. On the other hand, the Java * IDE would not save the image builder state on a snapshot because * that information is non-essential; in the unlikely event of a crash, * the image should be rebuilt either from scratch or from the last saved * state. *

* The following snippet shows how a plug-in participant would write * its important state to a file whose name is based on the save * number for this save operation.

*
	 *     Plugin plugin = ...; // known
	 *     int saveNumber = context.getSaveNumber();
	 *     String saveFileName = "save-" + Integer.toString(saveNumber);
	 *     File f = plugin.getStateLocation().append(saveFileName).toFile();
	 *     plugin.writeImportantState(f);
	 *     context.map(IPath.fromOSString("save"), IPath.fromOSString(saveFileName));
	 *     context.needSaveNumber();
	 *     context.needDelta(); // optional
	 * 
*

* When the plug-in is reactivated in a subsequent workspace session, * it needs to re-register to participate in workspace saves. When it * does so, it is handed back key information about what state it had last * saved. If it's interested, it can also ask for a resource delta * describing all resource changes that have happened since then, if this * information is still available. * The following snippet shows what a participant plug-in would * need to do if and when it is reactivated: *

*
	 *     IWorkspace ws = ...; // known
	 *     Plugin plugin = ...; // known
	 *     ISaveParticipant saver = ...; // known
	 *     ISavedState ss = ws.addSaveParticipant(plugin, saver);
	 *     if (ss == null) {
	 *         // activate for very first time
	 *         plugin.buildState();
	 *     } else {
	 *         String saveFileName = ss.lookup(IPath.fromOSString("save"));
	 *         File f = plugin.getStateLocation().append(saveFileName).toFile();
	 *         plugin.readImportantState(f);
	 *         IResourceChangeListener listener = new IResourceChangeListener() {
	 *             public void resourceChanged(IResourceChangeEvent event) {
	 *                 IResourceDelta delta = event.getDelta();
	 *                 if (delta != null) {
	 *                     // fast reactivation using delta
	 *                     plugin.updateState(delta);
	 *                 } else {
	 *                     // slower reactivation without benefit of delta
	 *                     plugin.rebuildState();
	 *                 }
	 *         };
	 *         ss.processResourceChangeEvents(listener);
	 *     }
	 * 
* * @param context the save context object * @exception CoreException if this method fails * @see ISaveContext#getSaveNumber() */ void saving(ISaveContext context) throws CoreException; }




© 2015 - 2024 Weber Informatics LLC | Privacy Policy