Example usage for org.springframework.transaction.support AbstractPlatformTransactionManager subclass-usage

List of usage examples for org.springframework.transaction.support AbstractPlatformTransactionManager subclass-usage

Introduction

In this page you can find the example usage for org.springframework.transaction.support AbstractPlatformTransactionManager subclass-usage.

Usage

From source file com.turbospaces.spaces.tx.SpaceTransactionManager.java

/**
 * Space transaction manager allow you to communicate with {@link JSpace} transactionally.
 * Currently nested transactions are not allowed and not supported - however this can be changed in future releases.
 * 
 * @since 0.1
 */

From source file com.p5solutions.core.jpa.orm.transaction.TransactionManager.java

@Deprecated
// REMOVE
public class TransactionManager extends AbstractPlatformTransactionManager
        implements ResourceTransactionManager, BeanFactoryAware, InitializingBean {

    /**

From source file org.develspot.data.orientdb.transaction.OrientDBTransactionManager.java

@SuppressWarnings("serial")
public class OrientDBTransactionManager extends AbstractPlatformTransactionManager
        implements ResourceTransactionManager {

    public OrientDBTransactionManager(IOrientDataSource orientDataSource) {
        //TODO allow nested transactions

From source file com.alibaba.cobar.client.transaction.MultipleDataSourcesTransactionManager.java

/**
 * use {@link org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy} to wrap all of the data sources we
 * may use in TransactionManager and DAOs. {@link org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy}
 * will only fetch a connection when first statement get executed. So even we
 * start transaction on such data sources which are wrapped by
 * {@link org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy}, there is no performance penalty at

From source file org.topazproject.otm.spring.OtmTransactionManager.java

/**
 * A Spring transaction-manager that uses OTM transactions. Due to the current limitations on
 * Mulgara transactions, and hence current limitations on OTM transactions, this transaction
 * manager does not support suspending transactions or nested transactions (i.e. you can't use
 * propagation REQUIRES_NEW, NOT_SUPPORTED, or NESTED); however it does support re-using existing
 * transactions (i.e. you can use propagation REQUIRED, SUPPORTS, MANDATORY, and NEVER).

From source file org.springextensions.neodatis.NeoDatisTransactionManager.java

/**
 * 
 * @author Joerg Bellmann
 *
 */
@SuppressWarnings("serial")

From source file org.grails.datastore.mapping.transactions.DatastoreTransactionManager.java

/**
 * A {@link org.springframework.transaction.PlatformTransactionManager} instance that
 * works with the Spring datastore abstraction
 *
 * @author Graeme Rocher
 * @since 1.0

From source file org.springextensions.db4o.Db4oTransactionManager.java

/**
 * PlatformTransactionManager implementation for db4o.
 * <p/>
 * <p/>
 * This local strategy is an alternative to executing db4o operations within JTA
 * transactions. Its advantage is the ability to work in any environment,

From source file org.fcrepo.camel.FcrepoTransactionManager.java

/**
 * A Transaction Manager for interacting with fedora-based transactions
 *
 * @author Aaron Coburn
 * @since Feb 16, 2015
 */

From source file com._4dconcept.springframework.data.marklogic.datasource.ContentSourceTransactionManager.java

/**
 * {@link org.springframework.transaction.PlatformTransactionManager}
 * implementation for a single XDBC {@link ContentSource}. This class is
 * capable of working in any environment with any XDBC driver, as long as the setup
 * uses a {@code com.marklogic.xcc.ContentSource} as its {@code Session} factory mechanism.
 * Binds a XDBC Session from the specified ContentSource to the current thread,