Internal Website Search

Regarding to Transactions. The need for an extended persistence Context emerges for the need ... to begin a new transaction when a transaction is active. In principal The SF doesn't need to begin any transaction since it only get called by the SL which can control it So I tried

at a time. The transaction obtained from the PersistentManager is commited after persisting 200 records and then the same transaction object from the same PersistentManager is used to begin the transaction. With objectdb 2.x do we need to close the PersistentManager

.java:517) at org.springframework.transaction.support.AbstractPlatformTransactionManager ... ="pre-java"> @Transactional     @Override     public TrackerUser ... I found some other nice exceptions: @Transactional   

) Attempt to start a transaction while another transaction is running. In each case, I've ... .database.ObjectDbDatabase.transact(ObjectDbDatabase.groovy:82) at app.framework.Database$transact.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall

performance problems when it came to transactions with lots of entities. We have a scenario ... > When do this within one transaction without holding a reference on the retrived entities ... the transaction after a certain number of read accesses (every 10000 read access to commit and open a new

class="description"> Indicate whether a resource transaction is in progress. transaction is in progress Throws

> Determine whether the current resource transaction has been marked ... > boolean indicating whether the transaction has been marked for rollback

that transactions are managed by the Java Transactions API, as documented in JSR-220.

> if there is one. Transactional and persistent instances return the associated PersistenceManager . Transient non-transactional instances and instances of classes that do not

returned is only valid within the current transaction. transaction. Since: