CoreandServices.book - Ocean - Schlumberger

Data Management
The ITransaction interface is defined as:
public interface ITransaction : IDisposable
{
object Context { get; }
ITransactionManager Manager { get; }
void Abandon ();
void Abandon (out Collection exceptions);
void Commit ();
void Commit (out Collection exceptions);
void Lock (params object[ ] objects);
void LockCollection (IEnumerable objectCollection);
bool TryLock (params object [ ] objects);
bool TryLockCollection (IEnumerable objectCollection);
event EventHandler ObjectLocked;
event EventHandler TransactionAbandoned;
event EventHandler TransactionAbandoning;
event EventHandler TransactionCommitted;
event EventHandler TransactionCommitting;
}
Once a transaction has been created and the reference to the ITransaction object has
been returned, you can perform the methods of ITransaction according to your needs
and some basic rules. The rules are:
• Objects that are being updated or deleted must be locked first. If it is not locked and an
attempt is made to modify the object, then a TransactionException exception will
be thrown.
• When an object is going to be created as the child of another object, then the parent
object must be locked before the creation.
• When an object is created inside a transaction, it is implicitly locked. For example, if you
create an object and then want to modify its name, you do not have to lock it. The lock
you placed on its parent before the creation carries through to the new child.
Any object can be locked in a transaction. It is the responsibility of the
ITransactionManager and ITransaction implementations in the product family to
manage the mechanics of locking objects.
Schlumberger Private
Ocean Core 3-61