net.sf.mmm.transaction.api (JavaDocs for mmm-all dev-SNAPSHOT)

Interface Summary
Interface	Description
TransactionAdapter	This interface adapts underlying transactions.
TransactionCallable<RESULT>	This interface is like a `Callable` but gets a `TransactionAdapter` as argument in order to do `intermediate commits` (e.g.
TransactionContext	This is the interface for a context for custom-data associated with an `TransactionAdapter`.
TransactionEvent	This is the `Event` send if a transaction has been `committed` or `rolled back`.
TransactionEventListener	This is the interface for a `listener` of `TransactionEvent`s.
TransactionExecutor	This is the interface for a component capable of executing your code within a transaction.

Class Summary
Class Description

TransactionSettings
This class is a simple bean that can be used to configure transactions used by the TransactionExecutor.

Class Summary
Class	Description
TransactionSettings	This class is a simple bean that can be used to configure transactions used by the `TransactionExecutor`.

Enum Summary
Enum	Description
TransactionEventType	This enum contains the available `types` of `TransactionEvent`s.
TransactionIsolationLevel	This enum contains the available isolation-levels for a transaction as defined by`Connection.getTransactionIsolation()`.

Package net.sf.mmm.transaction.api Description

Provides the API for transaction support.

Transaction API

This package contains the API for transaction support. For scenarios where AOP is not an option (for what ever reason) mmm-transaction supports simple and effective transaction management and prevents you from doing typical mistakes when dealing with transactions.
The main component offered by this API is TransactionExecutor that allows to perform arbitrary code within a transaction. Use this at the entry points to your application (web-services, servlets, etc.). For advanced use-cases like batches that have to process millions of entities you can use the TransactionCallable callback-interface to delegate to your custom code to execute transactional. Then you will receive a TransactionAdapter that allows to do intermediate commits without bundling your business logic with the technical details of transaction handling. Additionally, TransactionExecutor allows to register an TransactionEventListener to add custom logic to the transaction management.
This API abstracts from any underlying transaction management framework (JTA, spring-transaction) and allows to choose it by adding the right implementation of this API to your classpath.