You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2017/03/30 05:53:41 UTC

[jira] [Commented] (TAP5-2553) Support pseudo nested JPA transactions, injectable entity listeners and pre/post commit hooks

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

Jochen Kemnade commented on TAP5-2553:
--------------------------------------

[~kaosko], can we close this?

> Support pseudo nested JPA transactions, injectable entity listeners and pre/post commit hooks
> ---------------------------------------------------------------------------------------------
>
>                 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
(v6.3.15#6346)