Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 78841 invoked from network); 19 Feb 2010 16:50:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Feb 2010 16:50:51 -0000 Received: (qmail 24070 invoked by uid 500); 19 Feb 2010 16:50:51 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 24040 invoked by uid 500); 19 Feb 2010 16:50:51 -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 24030 invoked by uid 99); 19 Feb 2010 16:50:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 16:50:51 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 16:50:49 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E9AE529A0028 for ; Fri, 19 Feb 2010 08:50:27 -0800 (PST) Message-ID: <281382250.391281266598227956.JavaMail.jira@brutus.apache.org> Date: Fri, 19 Feb 2010 16:50:27 +0000 (UTC) From: "Timothy Ward (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Created: (OPENJPA-1524) ManagedRuntime does not work for OSGi MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org ManagedRuntime does not work for OSGi ------------------------------------- Key: OPENJPA-1524 URL: https://issues.apache.org/jira/browse/OPENJPA-1524 Project: OpenJPA Issue Type: Bug Components: osgi Affects Versions: 2.0.0-beta Reporter: Timothy Ward In an OSGi runtime there is no TransactionManager registered in JNDI It is possible to use an osgi:services/ lookup, but it is much safer, and better practice to look up the resource in the OSGi service registry. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.