tapestry-commits 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-2544) Using JPA EntityManager without explicit @PersistenceContext fails
Date Tue, 26 Apr 2016 15:27:12 GMT

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

ASF subversion and git services commented on TAP5-2544:
-------------------------------------------------------

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

TAP5-2544: Using JPA EntityManager without explicit @PersistenceContext
fails

- do not require the @PersistenceContext annotation to exist


> Using JPA EntityManager without explicit @PersistenceContext 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)

Mime
View raw message