[ARIES-1362] Support coordinations triggered by transaction markers

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: transaction-blueprint-1.0.2
• Fix Version/s: transaction-blueprint-1.1.0
• Component/s: Transaction
• Assignee: Christian Schneider
• Reporter: Christian Schneider
• Created: 27/Jul/15 15:53
• Updated: 11/Jun/21 06:03
• Resolved: 29/Jul/15 14:56

Description

The new JPA component uses coordinations to manage the lifecycle of the JPA EntityManager.
The blueprint transaction support should create a coordination for all transaction markers. This will allow the JPA entitymanager to have a controlled lifecycle that is larger than the DAO method.

So for example a service method that calls several DAO methods can be marked with @Transactional. It will then create a coordination for the method and close the EntityManager only after the whole service method.
If the service method does not need a transaction it can be annotated with TxType.SUPPORTS. In this case only the coordination will be started. So the EM lifecycle can be declared using an annotation without the performance impact of a transaction.

Issue Links

• relates to: ARIES-2050 Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations