Home » Search

About Transaction

131-140 of 200Refresh
JDO Doc
5

javax.jdo.listener.StoreLifecycleListener

during javax.jdo.PersistenceManager.flush or javax.jdo.Transaction.commit. Invoked whenever a persistent instance is stored, for example during javax.jdo.PersistenceManager.flush or javax.jdo.Transaction ... is stored, for example during javax.jdo.PersistenceManager.flush or javax.jdo.Transaction.commit
JPA Doc
5

javax.persistence.FlushModeType

Flush mode setting. When queries are executed within a transaction, if FlushModeType ... . If there is no transaction active, the persistence provider must not flush to the database. Since: JPA 1.0 ... execution. Since: JPA 1.0 FlushModeType COMMIT Flushing to occur at transaction commit. Flushing to occur
JDO Doc
5

jdoGetObjectId()

, then the ObjectId returned is only valid within the current transaction. If the JDO identity is being changed in the transaction, this method returns the object id as of the beginning of the current transaction. Returns: a copy of the ObjectId of this instance as of the beginning of the transaction. Since: JDO 1.0
JDO Doc
5

jdoGetTransactionalObjectId()

of the instance has not changed in the current transaction. If the JDO identity is being changed in the transaction, this method returns the current object id as modified in the current transaction. Returns: a copy of the ObjectId of this instance as modified in the transaction. Since: JDO 1.0
JPA Doc
5

joinTransaction()

that a JTA transaction is active. This method should be called on a JTA application managed entity manager that was created outside the scope of the active transaction to associate it with the current JTA transaction. Throws: TransactionRequiredException - if there is no transaction Since: JPA 1.0
JPA Doc
5

refresh(entity, lockMode)

locking failure causes transaction-level rollback the LockTimeoutException will be thrown ... is not managed TransactionRequiredException - if there is no transaction and if invoked on a container-managed EntityManager instance with PersistenceContextType.TRANSACTION or with a lock mode
JPA Doc
5

refresh(entity, lockMode, properties)

but cannot be locked: the PessimisticLockException will be thrown if the database locking failure causes transaction ... managed TransactionRequiredException - if there is no transaction and if invoked on a container-managed EntityManager instance with PersistenceContextType.TRANSACTION or with a lock mode
Issue
4

Unexpected exception (Error 990) com.objectdb.o.InternalException

$AjcClosure27.run(PatternApplicationServiceImpl.java:1) at com.btc.ep.base.transactions.annotations.TransactionAspect.ajc$around$com_btc_ep_base_transactions_annotations_TransactionAspect$1$adc4043cproceed(TransactionAspect.aj:90) at com.btc.ep.base.transactions.annotations.TransactionAspect.ajc
JDO Doc
4

checkConsistency()

with the datastore. This method has no effect if a transaction is not active. If a datastore transaction is active, this method verifies the consistency of instances in the cache against the datastore ... to do so. If an optimistic transaction is active, this method obtains a datastore connection and verifies
JDO Doc
4

Constants.TX_REPEATABLE_READ

Static Field javax.jdo.Constants String TX_REPEATABLE_READ Transaction isolation level representing the requirement to read the same data in the same transaction. Since: JDO 2.2 See Also: PersistenceManagerFactory.getTransactionIsolationLevel() Transaction.getIsolationLevel()