Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Received-SPF: pass (athena.apache.org: domain of cschneider111@gmail.com
 designates 209.85.217.181 as permitted sender)
Sender: Christian Schneider <cschneider111@gmail.com>
Message-ID: <544A3494.5050905@die-schneider.net>
Date: Fri, 24 Oct 2014 13:14:28 +0200
From: Christian Schneider <chris@die-schneider.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: dev@aries.apache.org
Subject: Discuss Release of aries jpa bundles
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

The last release of aries jpa fixes an important bug but is not 
compatible to jpa 2.0 providers anymore.
In the mean time we fixed this. So the current aries jpa trunk works 
well with jpa 2.0 and 2.1.

I would like to release the aries bundles as soon as possible to finally 
ship the fix to the bug below.
I created a feature snippet for karaf that you can use to quickly test 
the current snapshots as a drop in replacement for the jpa feature.

As we currently have quite a few different versions of the jpa bundles I 
would also like to sync the versions. So I propose we set all the jpa 
bundles to version 1.1.0. This would then also reflect that we now 
support jpa 2.1 which is not just a bugfix.

The current snapshot also includes some more improvements. For example 
the EntityManager in container.context now does not use synchronized all 
over the place (thanks to Guillaume) which was a severe performance 
bottleneck.

Christian

-----

     <feature name="jpa" description="OSGi Persistence Container" 
version="1.0.4" resolver="(obr)">
         <details>JPA implementation provided by Apache Aries JPA 1.0.4. 
NB: this feature doesn't provide the JPA engine, you have to install one 
by yourself (OpenJPA for instance)</details>
         <bundle dependency="true" 
start-level="30">mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1</bundle>
         <bundle dependency="true" 
start-level="30">mvn:org.apache.geronimo.specs/geronimo-jpa_2.0_spec/1.1</bundle>
         <bundle 
start-level="30">mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/1.0.3-SNAPSHOT</bundle>
         <bundle 
start-level="30">mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint.aries/1.0.4-SNAPSHOT</bundle>
         <bundle 
start-level="30">mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/1.0.2-SNAPSHOT</bundle>
         <bundle 
start-level="30">mvn:org.apache.aries.jpa/org.apache.aries.jpa.container.context/1.0.4-SNAPSHOT</bundle>
     </feature>

This is the main bug I would like to have solved in the new
https://issues.apache.org/jira/browse/ARIES-1160

-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com