You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Christian Schneider <ch...@die-schneider.net> on 2015/06/16 15:16:02 UTC
[VOTE] Release Aries JPA 2.0.0
I've staged a release for vote at:
https://repository.apache.org/content/repositorie/orgapachearies-1024/
This is the first release of Aries JPA on a sub project basis. So all
modules have the same version. Still the package versions are managed
separately using semantic versioning.
This version is a major redesign of the jpa modules.
Some of highlights:
1. Persistence Unit bundles can now be updated
2. DataSource and DataSourceFactory are now tracked as services. While
we still use the jndi syntax we are now fully dynamic. An EMF is only
created if the PersistenceProvider and DataSource are present
3. We now support a JPATemplate style that works nicely with Java 8
closures and makes it easy to use JPA with Declarative Services. See
examples
4. We now pass the OSGi TCK for jpa. The source contains a tck test
module that can be easily run by everyone with tck access
5. Support for @PersistenceContext and @PersistenceUnit annotations
For a detailed list of changes see:
https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
Release Notes - Aries - Version jpa-2.0.0
** Bug
* [ARIES-1023] - Construct a persistence unit with parameters
* [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for
context, or namespace handler looking for wrong namespace
* [ARIES-1162] - Persistence Units neet to be destroyed when bundle
becomes unresolved
* [ARIES-1270] - ClasscastException or incompatible type when
persistence unit bundle is refreshed
* [ARIES-1271] - EntityManager throws InvocationtargetException
instead of original cause
* [ARIES-1273] - Persistence unit with hibernate does not start if
datasource is not present
* [ARIES-1325] - Redesign of jpa component
* [ARIES-1337] - Avoid exception when closing an already closed EMF
** Improvement
* [ARIES-1294] - Refactor blueprint NSHandler
* [ARIES-1332] - Update to parent 2.0.1
* [ARIES-1335] - Avoid using aries util in eclipselink adapter
Please review and vote:
[ ] +1 Release Aries JPA 2.0.0
[ ] -1 Do not
Here is my +1
Cheers,
Christian
Re: [VOTE] Release Aries JPA 2.0.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
FYI (and ones interested by a build), the tag is:
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.jpa-2.0.0/
I'm running tests now.
Regards
JB
On 06/16/2015 03:16 PM, Christian Schneider wrote:
> I've staged a release for vote at:
> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>
> This is the first release of Aries JPA on a sub project basis. So all
> modules have the same version. Still the package versions are managed
> separately using semantic versioning.
>
> This version is a major redesign of the jpa modules.
> Some of highlights:
> 1. Persistence Unit bundles can now be updated
> 2. DataSource and DataSourceFactory are now tracked as services. While
> we still use the jndi syntax we are now fully dynamic. An EMF is only
> created if the PersistenceProvider and DataSource are present
> 3. We now support a JPATemplate style that works nicely with Java 8
> closures and makes it easy to use JPA with Declarative Services. See
> examples
> 4. We now pass the OSGi TCK for jpa. The source contains a tck test
> module that can be easily run by everyone with tck access
> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>
> For a detailed list of changes see:
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>
> Release Notes - Aries - Version jpa-2.0.0
>
> ** Bug
> * [ARIES-1023] - Construct a persistence unit with parameters
> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for
> context, or namespace handler looking for wrong namespace
> * [ARIES-1162] - Persistence Units neet to be destroyed when bundle
> becomes unresolved
> * [ARIES-1270] - ClasscastException or incompatible type when
> persistence unit bundle is refreshed
> * [ARIES-1271] - EntityManager throws InvocationtargetException
> instead of original cause
> * [ARIES-1273] - Persistence unit with hibernate does not start if
> datasource is not present
> * [ARIES-1325] - Redesign of jpa component
> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>
> ** Improvement
> * [ARIES-1294] - Refactor blueprint NSHandler
> * [ARIES-1332] - Update to parent 2.0.1
> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>
> Please review and vote:
> [ ] +1 Release Aries JPA 2.0.0
> [ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Release Aries JPA 2.0.0
Posted by Giuseppe Gerla <gi...@gmail.com>.
+1
Regards
Giuseppe
2015-06-16 15:16 GMT+02:00 Christian Schneider <ch...@die-schneider.net>:
> I've staged a release for vote at:
> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>
> This is the first release of Aries JPA on a sub project basis. So all
> modules have the same version. Still the package versions are managed
> separately using semantic versioning.
>
> This version is a major redesign of the jpa modules.
> Some of highlights:
> 1. Persistence Unit bundles can now be updated
> 2. DataSource and DataSourceFactory are now tracked as services. While we
> still use the jndi syntax we are now fully dynamic. An EMF is only created
> if the PersistenceProvider and DataSource are present
> 3. We now support a JPATemplate style that works nicely with Java 8
> closures and makes it easy to use JPA with Declarative Services. See
> examples
> 4. We now pass the OSGi TCK for jpa. The source contains a tck test module
> that can be easily run by everyone with tck access
> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>
> For a detailed list of changes see:
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>
> Release Notes - Aries - Version jpa-2.0.0
>
> ** Bug
> * [ARIES-1023] - Construct a persistence unit with parameters
> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for context,
> or namespace handler looking for wrong namespace
> * [ARIES-1162] - Persistence Units neet to be destroyed when bundle
> becomes unresolved
> * [ARIES-1270] - ClasscastException or incompatible type when
> persistence unit bundle is refreshed
> * [ARIES-1271] - EntityManager throws InvocationtargetException
> instead of original cause
> * [ARIES-1273] - Persistence unit with hibernate does not start if
> datasource is not present
> * [ARIES-1325] - Redesign of jpa component
> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>
> ** Improvement
> * [ARIES-1294] - Refactor blueprint NSHandler
> * [ARIES-1332] - Update to parent 2.0.1
> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>
> Please review and vote:
> [ ] +1 Release Aries JPA 2.0.0
> [ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
>
Re: [VOTE] Release Aries JPA 2.0.0
Posted by Jeremy Hughes <jp...@gmail.com>.
Hi, ok, thanks that all sounds good (err without actually trying it
:-) Thanks for clarifying.
Jeremy
On 18 June 2015 at 14:51, Christian Schneider <ch...@die-schneider.net> wrote:
> The current aries jpa (master) works quite well with updates of the
> persistence unit bundles.
> In the 1.x aries jpa I was never able to do a successful update because of
> this issue https://issues.apache.org/jira/browse/ARIES-1270 .
>
> In the new version the EntityManagers are closed after each request. If the
> persistence unit bundle is updated then the old EntityManagerFactory is
> unpublished and closed as soon as all EntityManagers are closed. At the same
> time a new EntityManagerFactory is published that will be picked up for any
> new transactions.
> So the implementation should not need Quiesce to be able to cope with
> updates.
>
> Additionally we still have the blueprint quiesce which will shut down all
> blueprint services that are the entry point for the acceses to jpa. So if
> you do a blueprint quiesce there should be no open EntityManager instances
> after a short period anyway.
>
> So with those two mechanisms I think there is no need to implement Quiesce
> in aries jpa 2.0 without loosing functionality.
> Besides that I have created a 1.x branch. So we will be able to maintain the
> old style bundles if people do not want to switch.
>
> The last argument is that the current implementation largely works without
> proxies of the EMF and EM. So it is a lot easier to understand and there is
> less room for problems. If we would implement Quiesce then we probably would
> have to introduce such proxies again with all the problems they bring.
>
> Christian
>
>
> On 18.06.2015 15:19, Jeremy Hughes wrote:
>>
>> Hi Sebastian, I guess I wasn't watching when the discussion happened
>> in April - sorry about that. We had a discussion before then about the
>> quiesce scenario with JPA. I see that the quiesce modules are no
>> longer used by JPA. Can you describe how quiesce is now achieved in
>> the new implementation. Without it, ie removing something users rely
>> on, I'd be a -1 on this release.
>>
>> Thanks,
>> Jeremy
>>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
Re: [VOTE] Release Aries JPA 2.0.0
Posted by Christian Schneider <ch...@die-schneider.net>.
The current aries jpa (master) works quite well with updates of the
persistence unit bundles.
In the 1.x aries jpa I was never able to do a successful update because
of this issue https://issues.apache.org/jira/browse/ARIES-1270 .
In the new version the EntityManagers are closed after each request. If
the persistence unit bundle is updated then the old EntityManagerFactory
is unpublished and closed as soon as all EntityManagers are closed. At
the same time a new EntityManagerFactory is published that will be
picked up for any new transactions.
So the implementation should not need Quiesce to be able to cope with
updates.
Additionally we still have the blueprint quiesce which will shut down
all blueprint services that are the entry point for the acceses to jpa.
So if you do a blueprint quiesce there should be no open EntityManager
instances after a short period anyway.
So with those two mechanisms I think there is no need to implement
Quiesce in aries jpa 2.0 without loosing functionality.
Besides that I have created a 1.x branch. So we will be able to maintain
the old style bundles if people do not want to switch.
The last argument is that the current implementation largely works
without proxies of the EMF and EM. So it is a lot easier to understand
and there is less room for problems. If we would implement Quiesce then
we probably would have to introduce such proxies again with all the
problems they bring.
Christian
On 18.06.2015 15:19, Jeremy Hughes wrote:
> Hi Sebastian, I guess I wasn't watching when the discussion happened
> in April - sorry about that. We had a discussion before then about the
> quiesce scenario with JPA. I see that the quiesce modules are no
> longer used by JPA. Can you describe how quiesce is now achieved in
> the new implementation. Without it, ie removing something users rely
> on, I'd be a -1 on this release.
>
> Thanks,
> Jeremy
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [VOTE] Release Aries JPA 2.0.0
Posted by Jeremy Hughes <hu...@apache.org>.
Hi Sebastian, I guess I wasn't watching when the discussion happened
in April - sorry about that. We had a discussion before then about the
quiesce scenario with JPA. I see that the quiesce modules are no
longer used by JPA. Can you describe how quiesce is now achieved in
the new implementation. Without it, ie removing something users rely
on, I'd be a -1 on this release.
Thanks,
Jeremy
On 16 June 2015 at 14:16, Christian Schneider <ch...@die-schneider.net> wrote:
> I've staged a release for vote at:
> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>
> This is the first release of Aries JPA on a sub project basis. So all
> modules have the same version. Still the package versions are managed
> separately using semantic versioning.
>
> This version is a major redesign of the jpa modules.
> Some of highlights:
> 1. Persistence Unit bundles can now be updated
> 2. DataSource and DataSourceFactory are now tracked as services. While we
> still use the jndi syntax we are now fully dynamic. An EMF is only created
> if the PersistenceProvider and DataSource are present
> 3. We now support a JPATemplate style that works nicely with Java 8 closures
> and makes it easy to use JPA with Declarative Services. See examples
> 4. We now pass the OSGi TCK for jpa. The source contains a tck test module
> that can be easily run by everyone with tck access
> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>
> For a detailed list of changes see:
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>
> Release Notes - Aries - Version jpa-2.0.0
>
> ** Bug
> * [ARIES-1023] - Construct a persistence unit with parameters
> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for context,
> or namespace handler looking for wrong namespace
> * [ARIES-1162] - Persistence Units neet to be destroyed when bundle
> becomes unresolved
> * [ARIES-1270] - ClasscastException or incompatible type when
> persistence unit bundle is refreshed
> * [ARIES-1271] - EntityManager throws InvocationtargetException instead
> of original cause
> * [ARIES-1273] - Persistence unit with hibernate does not start if
> datasource is not present
> * [ARIES-1325] - Redesign of jpa component
> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>
> ** Improvement
> * [ARIES-1294] - Refactor blueprint NSHandler
> * [ARIES-1332] - Update to parent 2.0.1
> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>
> Please review and vote:
> [ ] +1 Release Aries JPA 2.0.0
> [ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
Re: [VOTE] Release Aries JPA 2.0.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 (binding)
Tests passed.
Regards
JB
On 06/16/2015 03:16 PM, Christian Schneider wrote:
> I've staged a release for vote at:
> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>
> This is the first release of Aries JPA on a sub project basis. So all
> modules have the same version. Still the package versions are managed
> separately using semantic versioning.
>
> This version is a major redesign of the jpa modules.
> Some of highlights:
> 1. Persistence Unit bundles can now be updated
> 2. DataSource and DataSourceFactory are now tracked as services. While
> we still use the jndi syntax we are now fully dynamic. An EMF is only
> created if the PersistenceProvider and DataSource are present
> 3. We now support a JPATemplate style that works nicely with Java 8
> closures and makes it easy to use JPA with Declarative Services. See
> examples
> 4. We now pass the OSGi TCK for jpa. The source contains a tck test
> module that can be easily run by everyone with tck access
> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>
> For a detailed list of changes see:
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>
> Release Notes - Aries - Version jpa-2.0.0
>
> ** Bug
> * [ARIES-1023] - Construct a persistence unit with parameters
> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for
> context, or namespace handler looking for wrong namespace
> * [ARIES-1162] - Persistence Units neet to be destroyed when bundle
> becomes unresolved
> * [ARIES-1270] - ClasscastException or incompatible type when
> persistence unit bundle is refreshed
> * [ARIES-1271] - EntityManager throws InvocationtargetException
> instead of original cause
> * [ARIES-1273] - Persistence unit with hibernate does not start if
> datasource is not present
> * [ARIES-1325] - Redesign of jpa component
> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>
> ** Improvement
> * [ARIES-1294] - Refactor blueprint NSHandler
> * [ARIES-1332] - Update to parent 2.0.1
> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>
> Please review and vote:
> [ ] +1 Release Aries JPA 2.0.0
> [ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Release Aries JPA 2.0.0
Posted by David Bosschaert <da...@gmail.com>.
+1
David
On 16 June 2015 at 14:16, Christian Schneider <ch...@die-schneider.net> wrote:
> I've staged a release for vote at:
> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>
> This is the first release of Aries JPA on a sub project basis. So all
> modules have the same version. Still the package versions are managed
> separately using semantic versioning.
>
> This version is a major redesign of the jpa modules.
> Some of highlights:
> 1. Persistence Unit bundles can now be updated
> 2. DataSource and DataSourceFactory are now tracked as services. While we
> still use the jndi syntax we are now fully dynamic. An EMF is only created
> if the PersistenceProvider and DataSource are present
> 3. We now support a JPATemplate style that works nicely with Java 8 closures
> and makes it easy to use JPA with Declarative Services. See examples
> 4. We now pass the OSGi TCK for jpa. The source contains a tck test module
> that can be easily run by everyone with tck access
> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>
> For a detailed list of changes see:
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>
> Release Notes - Aries - Version jpa-2.0.0
>
> ** Bug
> * [ARIES-1023] - Construct a persistence unit with parameters
> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for context,
> or namespace handler looking for wrong namespace
> * [ARIES-1162] - Persistence Units neet to be destroyed when bundle
> becomes unresolved
> * [ARIES-1270] - ClasscastException or incompatible type when
> persistence unit bundle is refreshed
> * [ARIES-1271] - EntityManager throws InvocationtargetException instead
> of original cause
> * [ARIES-1273] - Persistence unit with hibernate does not start if
> datasource is not present
> * [ARIES-1325] - Redesign of jpa component
> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>
> ** Improvement
> * [ARIES-1294] - Refactor blueprint NSHandler
> * [ARIES-1332] - Update to parent 2.0.1
> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>
> Please review and vote:
> [ ] +1 Release Aries JPA 2.0.0
> [ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
[RESULT][VOTE] Result Release Aries JPA 2.0.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Just to the tracking, I set e-mail subject to [RESULT].
Regards
JB
On 06/19/2015 02:42 PM, Christian Schneider wrote:
> This vote passes with 5 binding +1 (Christian Schneider, Jean-Baptiste
> Onofré, David Bosschaert, Daniel Kulp, Sergey Beryozkin),
> 1 non binding +1 (Giuseppe Gerla) and no other votes.
>
> I get the artifacts published.
> I also just pushed the updated jpa feature for karaf 4.
>
> Cheers
> Christian
>
> On 16.06.2015 15:16, Christian Schneider wrote:
>> I've staged a release for vote at:
>> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>>
>> This is the first release of Aries JPA on a sub project basis. So all
>> modules have the same version. Still the package versions are managed
>> separately using semantic versioning.
>>
>> This version is a major redesign of the jpa modules.
>> Some of highlights:
>> 1. Persistence Unit bundles can now be updated
>> 2. DataSource and DataSourceFactory are now tracked as services. While
>> we still use the jndi syntax we are now fully dynamic. An EMF is only
>> created if the PersistenceProvider and DataSource are present
>> 3. We now support a JPATemplate style that works nicely with Java 8
>> closures and makes it easy to use JPA with Declarative Services. See
>> examples
>> 4. We now pass the OSGi TCK for jpa. The source contains a tck test
>> module that can be easily run by everyone with tck access
>> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>>
>> For a detailed list of changes see:
>> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>>
>> Release Notes - Aries - Version jpa-2.0.0
>>
>> ** Bug
>> * [ARIES-1023] - Construct a persistence unit with parameters
>> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for
>> context, or namespace handler looking for wrong namespace
>> * [ARIES-1162] - Persistence Units neet to be destroyed when
>> bundle becomes unresolved
>> * [ARIES-1270] - ClasscastException or incompatible type when
>> persistence unit bundle is refreshed
>> * [ARIES-1271] - EntityManager throws InvocationtargetException
>> instead of original cause
>> * [ARIES-1273] - Persistence unit with hibernate does not start if
>> datasource is not present
>> * [ARIES-1325] - Redesign of jpa component
>> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>>
>> ** Improvement
>> * [ARIES-1294] - Refactor blueprint NSHandler
>> * [ARIES-1332] - Update to parent 2.0.1
>> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>>
>> Please review and vote:
>> [ ] +1 Release Aries JPA 2.0.0
>> [ ] -1 Do not
>>
>> Here is my +1
>>
>> Cheers,
>> Christian
>>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Result Release Aries JPA 2.0.0
Posted by Christian Schneider <ch...@die-schneider.net>.
This vote passes with 5 binding +1 (Christian Schneider, Jean-Baptiste
Onofré, David Bosschaert, Daniel Kulp, Sergey Beryozkin),
1 non binding +1 (Giuseppe Gerla) and no other votes.
I get the artifacts published.
I also just pushed the updated jpa feature for karaf 4.
Cheers
Christian
On 16.06.2015 15:16, Christian Schneider wrote:
> I've staged a release for vote at:
> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>
> This is the first release of Aries JPA on a sub project basis. So all
> modules have the same version. Still the package versions are managed
> separately using semantic versioning.
>
> This version is a major redesign of the jpa modules.
> Some of highlights:
> 1. Persistence Unit bundles can now be updated
> 2. DataSource and DataSourceFactory are now tracked as services. While
> we still use the jndi syntax we are now fully dynamic. An EMF is only
> created if the PersistenceProvider and DataSource are present
> 3. We now support a JPATemplate style that works nicely with Java 8
> closures and makes it easy to use JPA with Declarative Services. See
> examples
> 4. We now pass the OSGi TCK for jpa. The source contains a tck test
> module that can be easily run by everyone with tck access
> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>
> For a detailed list of changes see:
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>
> Release Notes - Aries - Version jpa-2.0.0
>
> ** Bug
> * [ARIES-1023] - Construct a persistence unit with parameters
> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for
> context, or namespace handler looking for wrong namespace
> * [ARIES-1162] - Persistence Units neet to be destroyed when
> bundle becomes unresolved
> * [ARIES-1270] - ClasscastException or incompatible type when
> persistence unit bundle is refreshed
> * [ARIES-1271] - EntityManager throws InvocationtargetException
> instead of original cause
> * [ARIES-1273] - Persistence unit with hibernate does not start if
> datasource is not present
> * [ARIES-1325] - Redesign of jpa component
> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>
> ** Improvement
> * [ARIES-1294] - Refactor blueprint NSHandler
> * [ARIES-1332] - Update to parent 2.0.1
> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>
> Please review and vote:
> [ ] +1 Release Aries JPA 2.0.0
> [ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [VOTE] Release Aries JPA 2.0.0
Posted by Sergey Beryozkin <sb...@gmail.com>.
+1
Sergey
>
>
>> On Jun 16, 2015, at 9:16 AM, Christian Schneider <ch...@die-schneider.net> wrote:
>>
>> I've staged a release for vote at:
>> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>>
>> This is the first release of Aries JPA on a sub project basis. So all modules have the same version. Still the package versions are managed separately using semantic versioning.
>>
>> This version is a major redesign of the jpa modules.
>> Some of highlights:
>> 1. Persistence Unit bundles can now be updated
>> 2. DataSource and DataSourceFactory are now tracked as services. While we still use the jndi syntax we are now fully dynamic. An EMF is only created if the PersistenceProvider and DataSource are present
>> 3. We now support a JPATemplate style that works nicely with Java 8 closures and makes it easy to use JPA with Declarative Services. See examples
>> 4. We now pass the OSGi TCK for jpa. The source contains a tck test module that can be easily run by everyone with tck access
>> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>>
>> For a detailed list of changes see:
>> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>>
>> Release Notes - Aries - Version jpa-2.0.0
>>
>> ** Bug
>> * [ARIES-1023] - Construct a persistence unit with parameters
>> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for context, or namespace handler looking for wrong namespace
>> * [ARIES-1162] - Persistence Units neet to be destroyed when bundle becomes unresolved
>> * [ARIES-1270] - ClasscastException or incompatible type when persistence unit bundle is refreshed
>> * [ARIES-1271] - EntityManager throws InvocationtargetException instead of original cause
>> * [ARIES-1273] - Persistence unit with hibernate does not start if datasource is not present
>> * [ARIES-1325] - Redesign of jpa component
>> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>>
>> ** Improvement
>> * [ARIES-1294] - Refactor blueprint NSHandler
>> * [ARIES-1332] - Update to parent 2.0.1
>> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>>
>> Please review and vote:
>> [ ] +1 Release Aries JPA 2.0.0
>> [ ] -1 Do not
>>
>> Here is my +1
>>
>> Cheers,
>> Christian
>>
>
Re: [VOTE] Release Aries JPA 2.0.0
Posted by Daniel Kulp <dk...@apache.org>.
+1
Dan
> On Jun 16, 2015, at 9:16 AM, Christian Schneider <ch...@die-schneider.net> wrote:
>
> I've staged a release for vote at:
> https://repository.apache.org/content/repositorie/orgapachearies-1024/
>
> This is the first release of Aries JPA on a sub project basis. So all modules have the same version. Still the package versions are managed separately using semantic versioning.
>
> This version is a major redesign of the jpa modules.
> Some of highlights:
> 1. Persistence Unit bundles can now be updated
> 2. DataSource and DataSourceFactory are now tracked as services. While we still use the jndi syntax we are now fully dynamic. An EMF is only created if the PersistenceProvider and DataSource are present
> 3. We now support a JPATemplate style that works nicely with Java 8 closures and makes it easy to use JPA with Declarative Services. See examples
> 4. We now pass the OSGi TCK for jpa. The source contains a tck test module that can be easily run by everyone with tck access
> 5. Support for @PersistenceContext and @PersistenceUnit annotations
>
> For a detailed list of changes see:
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332388
>
> Release Notes - Aries - Version jpa-2.0.0
>
> ** Bug
> * [ARIES-1023] - Construct a persistence unit with parameters
> * [ARIES-1079] - The jpa.xsd incorrectly specifies bp:map for context, or namespace handler looking for wrong namespace
> * [ARIES-1162] - Persistence Units neet to be destroyed when bundle becomes unresolved
> * [ARIES-1270] - ClasscastException or incompatible type when persistence unit bundle is refreshed
> * [ARIES-1271] - EntityManager throws InvocationtargetException instead of original cause
> * [ARIES-1273] - Persistence unit with hibernate does not start if datasource is not present
> * [ARIES-1325] - Redesign of jpa component
> * [ARIES-1337] - Avoid exception when closing an already closed EMF
>
> ** Improvement
> * [ARIES-1294] - Refactor blueprint NSHandler
> * [ARIES-1332] - Update to parent 2.0.1
> * [ARIES-1335] - Avoid using aries util in eclipselink adapter
>
> Please review and vote:
> [ ] +1 Release Aries JPA 2.0.0
> [ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com