[ https://issues.apache.org/jira/browse/ARIES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved ARIES-1362. ---------------------------------------- Resolution: Fixed > Support coordinations triggered by transaction markers > ------------------------------------------------------ > > Key: ARIES-1362 > URL: https://issues.apache.org/jira/browse/ARIES-1362 > Project: Aries > Issue Type: New Feature > Components: Transaction > Affects Versions: transaction-blueprint-1.0.2 > Reporter: Christian Schneider > Assignee: Christian Schneider > Fix For: transaction-blueprint-1.1.0 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)