Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 12624 invoked from network); 29 Oct 2009 20:46:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Oct 2009 20:46:45 -0000 Received: (qmail 64398 invoked by uid 500); 29 Oct 2009 20:46:45 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 64354 invoked by uid 500); 29 Oct 2009 20:46:45 -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 64344 invoked by uid 99); 29 Oct 2009 20:46:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Oct 2009 20:46:45 +0000 X-ASF-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [76.13.13.40] (HELO smtp101.prem.mail.ac4.yahoo.com) (76.13.13.40) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 29 Oct 2009 20:46:41 +0000 Received: (qmail 67944 invoked from network); 29 Oct 2009 20:46:19 -0000 Received: from cpe-174-099-058-061.nc.res.rr.com (dwoods@174.99.58.61 with plain) by smtp101.prem.mail.ac4.yahoo.com with SMTP; 29 Oct 2009 13:46:19 -0700 PDT X-Yahoo-SMTP: sCI.ryiswBB7FW.DxjU523c87MI- X-YMail-OSG: P6FnXskVM1kAjqR5OisBVZHRq7EJMxOFpe0ewFU0B5Qo.UOJIQoSOVnLQzZalU0H96w1RDfcuvhXYEmH68IYxVNRWSzfx_ueRwwWM1TTEBSmiSbnjWOOmfUIdyYLRd6hYfsY3UiTFUSDts_3TeDoOqq13Yqs08MGdykJ6PZtYMNy1_g36fDPFlhEoaP74gAUMhzhEv8hH4KjYX12nTBPUroq95U5ROEwOIfCIfcM3F7lpNFVCKFpdlapy2yuqrBrTqmFnryR3hhd1f.bNS8NMPIMW_96bZmqyc.3tKPG0gAJBJVXEZ7AulMMKR92_5XjQXP.9AGdLJxCmEqyMXUnwx8f.wtb_IEj0fdPD_U_CTneDJWtlGc5xOD2ISD5adt9b2YMHNT.XdY6gjp1AyoiadU- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4AE9FF1A.1080405@apache.org> Date: Thu, 29 Oct 2009 16:46:18 -0400 From: Donald Woods User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: dev@openjpa.apache.org Subject: Re: OSGi Aware Persistence Provider implementation References: <22a059a60910290230p34ffdc6ap31cd22be879ca28@mail.gmail.com> <22a059a60910290249m6033b54ha0e7a77d96b25550@mail.gmail.com> <89c0c52c0910291021g41142692y185e181dc1a1dfc3@mail.gmail.com> <22a059a60910291058vd570f26w561d8271a5fbb756@mail.gmail.com> In-Reply-To: <22a059a60910291058vd570f26w561d8271a5fbb756@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Yes, I've been trying to work on this in my spare time, but it's really waiting for the OSGi EEG to publish an early access release of their upcoming specs (including RFC 143 for JPA support) before we can really work on this in a true open source manner.... OpenJPA trunk (2.0.0-SNAPSHOT) and the openjpa-osgi module would be the right place to target any patches for OSGi support, which we may backport to the 1.3.x branch later depending on the required changes. -Donald Milinda Pathirage wrote: > Thanks Kevin for your answers. I'm using OpenJPA in Apache ODE which runs in > a OSGi environment(WSO2 Carbon platform). I tried OpenJPA 2.0, but there > were some issues with ODE's JPA queries. I'll try to port current > implementation to work with OpenJPA 2.0. I also think that it's better if we > can add OSGi support for OpenJPA 2.0 because I saw there are fixes in > Geranimo JPA spec jar for OSGi related issues. I'll create a patch for OSGi > related class loading issues and attach it to a JIRA. > > Thanks in advance, > Milinda > > > On Thu, Oct 29, 2009 at 10:51 PM, Kevin Sutter wrote: > >> Hi Milinda, >> Yes, there is some interest in allowing OpenJPA usage in an OSGi container >> environment. It's just not a "full time job" for any of us at the >> moment... >> >> Porting the JDK 6 changes back to the 1.3.x release might cause some >> concern >> for those users of the 1.3.x branch. Many of the changes would now require >> the use of JDK 6 and we didn't want to force this onto the JPA 1.0 usage >> community. Thus, we limited the change to trunk for our JPA 2.0 >> development >> [1]. >> >> Is there any reason why your experimentation and changes couldn't be >> targeted for the JPA 2.0 implementation? I think you will find our current >> M3 driver is quite solid, especially as it pertains to existing JPA 1.0 >> functionality. Thus, any current JPA 1.0 applications should run unchanged >> with a JPA 2.0 driver. >> >> Thanks, >> Kevin >> >> [1] >> >> http://n2.nabble.com/DISCUSS-Drop-build-support-for-Java-5-td2539470i20.html#a3554445 >> >> >> On Thu, Oct 29, 2009 at 4:49 AM, Milinda Pathirage < >> milinda.pathirage@gmail.com> wrote: >> >>> Hi all, >>> I have another question. Is there any plan for fixing OpenJPA 1.3.x >>> compilation failures in JDK 1.6 >>> >>> Thanks >>> Milinda >>> >>> On Thu, Oct 29, 2009 at 3:00 PM, Milinda Pathirage < >>> milinda.pathirage@gmail.com> wrote: >>> >>>> We are currently using OpenJPA 1.1.0 in equinox OSGi container by >> making >>> it >>>> a fragment of the bundle which use it to fix the issue of loading >>>> persistence.xml. Now we want to use OpenJPA in two different OSGi >> bundles >>>> and fragment hack will not work in this situation. Current 1.3.x >> OpenJPA >>>> implementation also doesn't support OSGi aware resource loading. We can >>> fix >>>> this by following the method use by Eclipselink. In this method what we >>> have >>>> to do is implement a OSGi aware Persistence Provider by extending the >>>> current Persistence Provider implementation and introduce bundle >>> activator >>>> to register persistence provider service at bundle activation. This >> will >>> not >>>> break the existing functionality of OpenJPA in J2SE environment and >>> improve >>>> the support for OSGi containers. >>>> >>>> Are there any plans to add OSGi support, if there any I would like to >>> help. >>>> I'll provide a patch ASAP for this. >>>> >>>> Thanks >>>> Milinda >>>> >>>> -- >>>> Milinda Pathirage >>>> Senior Software Engineer & Product Manager WSO2 BPS; >> http://wso2.org/bps >>>> WSO2 Inc.; http://wso2.com >>>> E-mail: milinda@wso2.com, milinda.pathirage@gmail.com >>>> Web: http://mpathirage.com >>>> Blog: http://blog.mpathirage.com >>>> >>> >>> >>> -- >>> Milinda Pathirage >>> Senior Software Engineer & Product Manager WSO2 BPS; http://wso2.org/bps >>> WSO2 Inc.; http://wso2.com >>> E-mail: milinda@wso2.com, milinda.pathirage@gmail.com >>> Web: http://mpathirage.com >>> Blog: http://blog.mpathirage.com >>> > > >