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

Posted to dev@tapestry.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2016/04/26 17:22:13 UTC

[jira] [Updated] (TAP5-2544) Using JPA EntityManager without explicit @PersistentContext fails

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

Kalle Korhonen updated TAP5-2544:
---------------------------------
    Description: The issue was caused by a fix to TAP5-2027 and only affects 5.4.1 (and unreleased 5.5.x). As a workaround use 5.4.0 tapestry-jpa when you only have a single EntityManager.  (was: The issue was caused by a fix to TAP5-2027 and only affects 5.4.1 (and unreleased 5.5.x).)

> Using JPA EntityManager without explicit @PersistentContext fails
> -----------------------------------------------------------------
>
>                 Key: TAP5-2544
>                 URL: https://issues.apache.org/jira/browse/TAP5-2544
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-jpa
>    Affects Versions: 5.4.1
>            Reporter: Kalle Korhonen
>            Assignee: Kalle Korhonen
>
> The issue was caused by a fix to TAP5-2027 and only affects 5.4.1 (and unreleased 5.5.x). As a workaround use 5.4.0 tapestry-jpa when you only have a single EntityManager.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)