tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2553) Support pseudo nested JPA transactions, injectable entity listeners and pre/post commit hooks
Date Wed, 08 Jun 2016 17:06:21 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320940#comment-15320940

ASF subversion and git services commented on TAP5-2553:

Commit 5047220cfe9a6f8a640fb10f0e3de266af51630f in tapestry-5's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=5047220 ]

TAP5-2553: Support pseudo nested JPA transactions etc.

- add all classes from
- rename packages from net.satago.tapestry5.. to org.apache.tapestry5...
- replace code contents of all advice and worker related classes
(CommitAfterMethodAdvice, CommitAfterWorker, JpaTransactionAdvisorImpl)
with the new implementation
- manually merge relevant code from TransactionUnitsModule to JpaModule
- add new dependencies
- remove remaining net.satago. classes
- I could only make the JpaIntegrationTestWithAnnotationsInServiceImplementation test succeeded
by adding the @PersistenceContext
annotations to the app6.UserDAO interface, why is that?
- reformat code according to Tapestry guidelines

> Support pseudo nested JPA transactions, injectable entity listeners and pre/post commit
> ---------------------------------------------------------------------------------------------
>                 Key: TAP5-2553
>                 URL: https://issues.apache.org/jira/browse/TAP5-2553
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-jpa
>    Affects Versions: 5.4.1
>            Reporter: Kalle Korhonen
>            Assignee: Kalle Korhonen
>              Labels: jpa
>             Fix For: 5.5.0
> Plain JPA does not support nested transaction but by keeping track of @CommitAfter stack,
we can support "pseudo nested" transactions. The concept was first demonstrated in https://github.com/satago/tapestry-jpa-transactions.
@kaosko started an effort to merge the codebase to T5 (https://github.com/satago/tapestry-jpa-transactions/pull/5)
but because of fundamental limitations in the original design (no support for multiple persistence
units, pre/post commit hooks were only available for the last transaction), @kaosko refactored
the implementation for more general use (https://github.com/kaosko/tapestry-jpa-transactions).
The original code was under Apache license with support from the original authors to merge
the codebase to T5 and the refactored implementation was solely made by @kaosko. This issue
is about merging the refactored implementation to T5.5 and replacing the existing JPA classes
(mainly class workers, advisors) by the those provided by the new implementation.

This message was sent by Atlassian JIRA

View raw message