Uses of Interface
com.ultikits.ultitools.interfaces.JdbcTransactionManager
Packages that use JdbcTransactionManager
Package
Description
-
Uses of JdbcTransactionManager in com.ultikits.ultitools.interfaces.impl.data.mysql
Fields in com.ultikits.ultitools.interfaces.impl.data.mysql with type parameters of type JdbcTransactionManagerModifier and TypeFieldDescriptionprivate final Map<String, JdbcTransactionManager> MysqlDataStore.transactionManagerMapJdbcTransactionManagercache, keyed by requesting identity -- one manager per plugin container even though every plugin shares the one globalMysqlDataStore.dataSource(D-02):contextHolderis a per-instanceThreadLocal(FOUND-04), so two plugins each doing a@Transactionalwrite on MySQL must never cross transaction state, exactly asPluginManager.wireTransactional's own javadoc already documents for the JDBC path.Methods in com.ultikits.ultitools.interfaces.impl.data.mysql that return JdbcTransactionManagerModifier and TypeMethodDescriptionMysqlDataStore.transactionManagerFor(DataScope scope) Resolves the same per-plugin-containerJdbcTransactionManagerinstanceMysqlDataStore.getOperator(com.ultikits.ultitools.abstracts.UltiToolsPlugin, java.lang.Class<T>)wires onto the operators it hands out forscope's own identity -- the seamPluginManager.wireTransactionalcalls to bind the AOP@Transactionalinterceptor to it, so a module's data operators and its@Transactionalbeans share one transaction, not two (T-02-TAM-11), despite every plugin sharing the one globalMysqlDataStore.dataSource.private JdbcTransactionManagerMysqlDataStore.transactionManagerForIdentity(String identity) Returns the manager foridentity, building it on first touch. -
Uses of JdbcTransactionManager in com.ultikits.ultitools.interfaces.impl.data.sqlite
Fields in com.ultikits.ultitools.interfaces.impl.data.sqlite with type parameters of type JdbcTransactionManagerModifier and TypeFieldDescriptionprivate final Map<String, JdbcTransactionManager> SQLiteDataStore.transactionManagerMapJdbcTransactionManagercache, keyed identically toSQLiteDataStore.dataSourceMap-- the backing .db file's canonical path (D-02: one JDBCDataSourceper file already means one manager per file is "one per plugin container", since each plugin has its own file).Methods in com.ultikits.ultitools.interfaces.impl.data.sqlite that return JdbcTransactionManagerModifier and TypeMethodDescriptionSQLiteDataStore.transactionManagerFor(DataScope scope) Resolves the same per-plugin-containerJdbcTransactionManagerinstanceSQLiteDataStore.getOperator(com.ultikits.ultitools.abstracts.UltiToolsPlugin, java.lang.Class<T>)wires onto the operators it hands out forscope's own database file -- the seamPluginManager.wireTransactionalcalls to bind the AOP@Transactionalinterceptor to it, so a module's data operators and its@Transactionalbeans share one transaction, not two (T-02-TAM-11).private JdbcTransactionManagerSQLiteDataStore.transactionManagerForPath(String dbPath) Returns the manager fordbPath, building it on first touch -- the samecomputeIfAbsentsingle-construction guaranteeSQLiteDataStore.poolFor(String)already gives the connection pool for that file. -
Uses of JdbcTransactionManager in com.ultikits.ultitools.manager
Classes in com.ultikits.ultitools.manager that implement JdbcTransactionManagerModifier and TypeClassDescriptionclassDataSource-based implementation ofTransactionManager, and its JDBC-specific sub-interfaceJdbcTransactionManager.Methods in com.ultikits.ultitools.manager that return JdbcTransactionManagerModifier and TypeMethodDescriptionprivate static JdbcTransactionManagerPluginManager.resolveJdbcTransactionManager(DataStore dataStore, DataScope scope, DataSource dataSource) Resolves theJdbcTransactionManagerPluginManager.wireTransactional(com.ultikits.ultitools.context.SimpleContainer, com.ultikits.ultitools.manager.DataScope, com.ultikits.ultitools.aop.AopProxyResolver)should bind the AOP interceptor to, for a JDBC-capabledataStore(02-09, T-02-TAM-11).