Uses of Class
org.exolab.castor.jdo.TransactionAbortedException

Packages that use TransactionAbortedException
org.castor.persist   
org.exolab.castor.jdo The Java Data Objects API Version: $Revision: 6216 $ $Date: 2005-04-21 14:21:10 -0600 (Thu, 21 Apr 2005) $ Author: Assaf Arkin The class JDOManager provides the Castor JDO engine used for obtaining a database connection.  
org.exolab.castor.jdo.engine Implementation of the Castor JDO engine. 
 

Uses of TransactionAbortedException in org.castor.persist
 

Methods in org.castor.persist that throw TransactionAbortedException
protected abstract  void AbstractTransactionContext.commitConnections()
          The derived class must implement this method and commit all the connections used in this transaction.
protected abstract  void AbstractTransactionContext.closeConnections()
          The derived class must implement this method and close all the connections used in this transaction.
 boolean AbstractTransactionContext.prepare()
          Prepares the transaction prior to committing it. Indicates whether the transaction is read-only (i.e. no modified objects), can commit, or an error has occured and the transaction must be rolled back. This method performs actual storage into the persistence storage. Multiple calls to this method can be done, and do not release locks, allowing checkpoint to occur. An IllegalStateException is thrown if transaction is not in the proper state to perform this operation.
 void AbstractTransactionContext.commit()
          Commits all changes and closes the transaction releasing all locks on all objects. All objects are now transient. Must be called after a call to TransactionContext.prepare() has returned successfully. Throws an IllegalStateException when called without calling TransactionContext.prepare() first.
 void AbstractTransactionContext.close()
          Closes all Connections. Must be called before the end of the transaction in EJB environment or after commit in standalone case. Throws an IllegalStateException if this method has been called after the end of the transaction.
protected  void GlobalTransactionContext.commitConnections()
          The derived class must implement this method and commit all the connections used in this transaction. If the transaction could not commit fully or partially, this method will throw an TransactionAbortedException, causing a rollback to occur as the next step.
protected  void GlobalTransactionContext.closeConnections()
          The derived class must implement this method and close all the connections used in this transaction.
protected  void LocalTransactionContext.commitConnections()
          The derived class must implement this method and commit all the connections used in this transaction. If the transaction could not commit fully or partially, this method will throw an TransactionAbortedException, causing a rollback to occur as the next step.
protected  void LocalTransactionContext.closeConnections()
          The derived class must implement this method and close all the connections used in this transaction.
 boolean TransactionContext.prepare()
          Prepares the transaction prior to committing it.
 void TransactionContext.commit()
          Commits all changes and closes the transaction releasing all locks on all objects.
 void TransactionContext.close()
          Closes all Connections.
 

Uses of TransactionAbortedException in org.exolab.castor.jdo
 

Subclasses of TransactionAbortedException in org.exolab.castor.jdo
 class ObjectModifiedException
          Indicates transaction has been aborted as a result of object being modified by a concurrent transaction.
 

Methods in org.exolab.castor.jdo that throw TransactionAbortedException
 void Database.commit()
          Commits and closes the transaction.
 

Uses of TransactionAbortedException in org.exolab.castor.jdo.engine
 

Methods in org.exolab.castor.jdo.engine that throw TransactionAbortedException
abstract  void AbstractDatabaseImpl.commit()
          Commits and closes the transaction. All changes made to persistent objects during the transaction are made persistent; objects created during the transaction are made durable; and, objects removed during the transaction are removed from the database.

In other words, any modifications to any data objects which are queried/loaded/created/update to this database is automatically stored to the database and visible to subsequence transactions. (ie. update is solely used for long transaction support and should not be called for any data object queried/loaded/created in the this transaction.)

If the transaction cannot commit, the entire transaction rolls back and a TransactionAbortedException exception is thrown.

After this method returns, the transaction is closed and all persistent objects are transient. Using Database.begin() to open a new transaction will not restore objects to their persistent stage.

 void GlobalDatabaseImpl.commit()
           
 void LocalDatabaseImpl.commit()
           
 



Copyright 2008 null. All Rights Reserved.