/*
* Copyright (c) 2010-2012, 2014, 2016 Eike Stepper (Loehne, Germany) 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:
* Eike Stepper - initial API and implementation
* Simon McDuff - bug 201266
* Simon McDuff - bug 233314
* Simon McDuff - bug 247143
*/
package org.eclipse.emf.cdo.transaction;
import org.eclipse.emf.cdo.CDOObject;
import org.eclipse.emf.cdo.common.revision.delta.CDOFeatureDelta;
import org.eclipse.emf.cdo.view.CDOView;
/**
* A call-back interface that is called by a {@link CDOTransaction transaction} before {@link CDOObject objects} are
* attached, modified or detached.
*
* @see CDOPostEventTransactionHandler
* @author Eike Stepper
* @since 4.0
*/
public interface CDOTransactionHandler1 extends CDOTransactionHandlerBase
{
/**
* Called by a CDOTransaction
before an object is added. The implementor of this method is allowed
* to throw an unchecked exception that will propagate up to the operation that is about to add the object (thereby
* preventing the operation from successful completion).
*
* Note: Implementors must not start threads which access the {@link CDOView view} and wait for their
* completion since deadlocks can result. The following example causes a deadlock:
*
*
* getDisplay().syncExec(new Runnable() * { * public void run() * { * try * { * cdoObject.getName(); * } * catch (Exception ignore) * { * } * } * }); ** * If you need to synchronously execute threads which access the {@link CDOView view} you should use * {@link CDOAsyncTransactionHandler}. */ public void attachingObject(CDOTransaction transaction, CDOObject object); /** * Called by a
CDOTransaction
before an object is detached. The implementor of this method is
* allowed to throw an unchecked exception that will propagate up to the operation that is about to remove the object
* (thereby preventing the operation from completing successfully).
*
* Note: Implementors must not start threads which access the {@link CDOView view} and wait for their
* completion since deadlocks can result. The following example causes a deadlock:
*
*
* getDisplay().syncExec(new Runnable() * { * public void run() * { * try * { * cdoObject.getName(); * } * catch (Exception ignore) * { * } * } * }); ** * If you need to synchronously execute threads which access the {@link CDOView view} you should use * {@link CDOAsyncTransactionHandler}. */ public void detachingObject(CDOTransaction transaction, CDOObject object); /** * Called by a
CDOTransaction
before an object is modified. The implementor of this method is
* allowed to throw an unchecked exception that will propagate up to the operation that is about to modify the object
* (thereby preventing the operation from completing successfully).
*
* Note: Implementors must not start threads which access the {@link CDOView view} and wait for their
* completion since deadlocks can result. The following example causes a deadlock:
*
*
* getDisplay().syncExec(new Runnable() * { * public void run() * { * try * { * cdoObject.getName(); * } * catch (Exception ignore) * { * } * } * }); ** * If you need to synchronously execute threads which access the {@link CDOView view} you should use * {@link CDOAsyncTransactionHandler}. */ public void modifyingObject(CDOTransaction transaction, CDOObject object, CDOFeatureDelta featureDelta); /** * A call-back interface that is called by a {@link CDOTransaction transaction} before {@link CDOObject objects} are * attached, modified, undone or detached. * * @author Eike Stepper * @since 4.6 */ public interface WithUndo extends CDOTransactionHandler1 { /** * Called by a
CDOTransaction
before an object is modified. The implementor of this method is
* allowed to throw an unchecked exception that will propagate up to the operation that is about to modify the object
* (thereby preventing the operation from completing successfully).
*
* Note: Implementors must not start threads which access the {@link CDOView view} and wait for their
* completion since deadlocks can result. The following example causes a deadlock:
*
*
* getDisplay().syncExec(new Runnable() * { * public void run() * { * try * { * cdoObject.getName(); * } * catch (Exception ignore) * { * } * } * }); ** * If you need to synchronously execute threads which access the {@link CDOView view} you should use * {@link CDOAsyncTransactionHandler}. */ public void undoingObject(CDOTransaction transaction, CDOObject object, CDOFeatureDelta featureDelta); } }