I've staged a release for vote at:
https://repository.apache.org/content/repositories/orgapachearies-1039
Highlights:
The new release only provides JTA 1.2 Annoations (@Transactional) to
configure transactions. The new namespace has only one element tx:enable
that is used to activate the scanning of all defined blueprint beans for
transaction anntotations.
The outermost @Transactional in a call stack also defines the life of a
JTA EntityManager provided by Aries JPA. So you can annotate a service
method and so make sure the same EM is available throughout the calls on
the same thread.
By using @Transactional(TxType.Supports) transaction.blueprint only
creates a coordination. Still the EntityManager will remain open inside
the call stack.
The 2.0.0 version of transaction.blueprint bundle can be used together
with the 1.1.1 version to support the new and old behaviour in parallel.
Release Notes - Aries - Version transaction-blueprint-2.0.0
** Improvement
* [ARIES-1382] - Only allow jta annotations to configure transactions
* [ARIES-1413] - Switch to 2.0.0 namespace
https://issues.apache.org/jira/browse/ARIES/fixforversion/12333578
Please review and vote:
[ ] +1 Release the above artifacts
[ ] -1 Do not
Here is my +1
Cheers,
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
