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

Posted to dev@aries.apache.org by "Grzegorz Grzybek (Jira)" <ji...@apache.org> on 2022/09/30 12:06:00 UTC

[jira] [Updated] (ARIES-2073) Aries JPA 2.7 wrong behavior with SUPPORTS transaction methods

     [ https://issues.apache.org/jira/browse/ARIES-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grzegorz Grzybek updated ARIES-2073:
------------------------------------
    Fix Version/s: transaction-blueprint-2.3.1

> Aries JPA 2.7 <jpa:enable> wrong behavior with SUPPORTS transaction methods
> ---------------------------------------------------------------------------
>
>                 Key: ARIES-2073
>                 URL: https://issues.apache.org/jira/browse/ARIES-2073
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>    Affects Versions: jpa-2.7.3
>            Reporter: Grzegorz Grzybek
>            Assignee: Grzegorz Grzybek
>            Priority: Major
>             Fix For: transaction-blueprint-2.3.1
>
>
> When calling two methods, one with REQUIRES and one with SUPPORTS behaviour, JPA access in the 2nd method should look up the existing EM associated with previous coordination. No new coordination should be created.
> SUPPORTS case is one (of six) missing behavior after some work was done in ARIES-2050.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)