Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 906CDD087 for ; Thu, 19 Jul 2012 10:07:36 +0000 (UTC) Received: (qmail 67158 invoked by uid 500); 19 Jul 2012 10:07:36 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 66811 invoked by uid 500); 19 Jul 2012 10:07:36 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 66735 invoked by uid 99); 19 Jul 2012 10:07:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2012 10:07:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id E0C5E142856 for ; Thu, 19 Jul 2012 10:07:34 +0000 (UTC) Date: Thu, 19 Jul 2012 10:07:34 +0000 (UTC) From: "Erik Kis (JIRA)" To: dev@openjpa.apache.org Message-ID: <865297137.75060.1342692454923.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (OPENJPA-2234) EntityManager instance creation needs TX activity MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Erik Kis created OPENJPA-2234: --------------------------------- Summary: EntityManager instance creation needs TX activity Key: OPENJPA-2234 URL: https://issues.apache.org/jira/browse/OPENJPA-2234 Project: OpenJPA Issue Type: Bug Affects Versions: 2.0.1 Environment: - JDK 1.5 - Spring 3.1.1.RELEASE - Spring Data JPA 1.1 GA (issue confirmed on version 1.0.3) - Atomikos 3.7.0 - OpenJPA 2.0.1 - DB2 9.7 Reporter: Erik Kis While working with Spring Data, we came across a potential bug in OpenJPA. The bug was provoked by a query lookup module in Spring Data JPA, but it has it roots in AbstractBrokerFactory class, which seems to requires transaction existence in order to create EntityManager (which is contrary to JPA spec). I have already been in touch with Spring Data JPA author (where I filed a bug against Spring Data JPA) who actually pointed me to file a bug _here_. I have extensively documented my findings on this thread (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager), so I'll rather post the link, instead of repeating the whole thing here. All that being said, I am not entirely sure what actually happened and am no authority whatsoever on JPA spec. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira