2460 results
OpenSessionInViewInterceptor (Spring Data Neo4j 5.0.2.RELEASE API)
lazy loading inweb views despite the original transactions already being completed. This interceptor makes Neo4j OGM Sessions available via the current thread,which will be autodetected by transaction managers. It is suitable for servicelayer transactions via Neo4jTransactionManager. In contrast to O
RedisCacheManager.RedisCacheManagerBuilder (Spring Data Redis 2.0.2.RELEASE API)
to be pre initialized with current RedisCacheConfiguration. Enable RedisCaches to synchronize cache put/evict operations with ongoing Spring-managed transactions. Append a Map of cache name/RedisCacheConfiguration pairs to be pre initialized. Entry point for builder style RedisCacheManager configuration
SimpleResourceHolder (Spring AMQP 2.0.1.RELEASE API)
Central helper that manages resources per thread to be used by resource management code. Supports one resource per key without overwriting, that is, a resource needsto be removed before a new one can be set for the same key. Resource management code should check for thread-bound resources via has(Object)
AbstractMessageListenerContainer (Spring AMQP 2.0.1.RELEASE API)
stateful retry. Set a task executor for the container - used to create the consumers not atruntime. Set the transaction attribute to use when using an external transaction manager. Set the transaction manager to use. Setup the message listener to use. Stop the shared Connection, call doShutdown(), and close
ItemWriteListenerAdapter (Spring Batch 4.0.0.RELEASE API)
List) This will becalled before any transaction is committed, and beforeChunkListener.afterChunk(ChunkContext) Description copied from interface: ItemWriteListener Called if an error occurs while trying to write. Will be called inside atransaction, but the transaction will normally be rolled back. There
JpaFlowExecutionListener (Spring Web Flow 2.4.5.RELEASE API)
except for the final commit will, by default, be non-transactional. However, a flow may callinto a transactional service layer to fetch objects during the conversation in the context of a read-only systemtransaction if the underlying JPA Transaction Manager supports this. Spring's JPA TransactionManager does
DefaultItemFailureHandler (Spring Batch 4.0.0.RELEASE API)
to read. Description copied from interface: ItemWriteListener Called if an error occurs while trying to write. Will be called inside atransaction, but the transaction will normally be rolled back. There isno way to identify from this callback which of the items (if any) causedthe error.
ItemWriteListener (Spring Batch 4.0.0.RELEASE API)
This will becalled before any transaction is committed, and beforeChunkListener.afterChunk(ChunkContext) Called if an error occurs while trying to write. Will be called inside atransaction, but the transaction will normally be rolled back. There isno way to identify from this callback which of the items
ItemReader (Spring Batch 4.0.0.RELEASE API)
feasible becausewe need to support transactions in an asynchronous batch. Reads a piece of input data and advance to the next one. Reads a piece of input data and advance to the next one. Implementationsmust return null at the end of the inputdata set. In a transactional setting, caller might get the same
HibernateFlowExecutionListener (Spring Web Flow 2.4.5.RELEASE API)
database, applying a version check ifnecessary. Note: All data access except for the final commit will, by default, be non-transactional. However, a flow may callinto a transactional service layer to fetch objects during the conversation in the context of a read-only systemtransaction. In that case, the