[jira] [Commented] (ARIES-1345) Support jpa annotations on method and class
[ https://issues.apache.org/jira/browse/ARIES-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613572#comment-14613572 ] Giuseppe Gerla commented on ARIES-1345: --- To manage method annotation, I will check only methods with name that starts with "set", has 1 parameter and type of parameter is one of EntityManagerFactory (@PersistenceUnit), EntityManager, EmSupplier (@PersistenceContext) > Support jpa annotations on method and class > --- > > Key: ARIES-1345 > URL: https://issues.apache.org/jira/browse/ARIES-1345 > Project: Aries > Issue Type: Improvement > Components: JPA >Affects Versions: jpa-2.0.0 >Reporter: Christian Schneider >Assignee: Giuseppe Gerla > Fix For: jpa-2.1.0 > > > @PersistenceContext and @PersistenceUnit annotations can also be used on > method and class level. > On method level the annotation could be put on a setter. > On class level I am not sure how we would interpret it. I have not found any > good real life example for this so I propose to not support it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ARIES-1345) Support jpa annotations on method and class
[ https://issues.apache.org/jira/browse/ARIES-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giuseppe Gerla reassigned ARIES-1345: - Assignee: Giuseppe Gerla > Support jpa annotations on method and class > --- > > Key: ARIES-1345 > URL: https://issues.apache.org/jira/browse/ARIES-1345 > Project: Aries > Issue Type: Improvement > Components: JPA >Affects Versions: jpa-2.0.0 >Reporter: Christian Schneider >Assignee: Giuseppe Gerla > Fix For: jpa-2.1.0 > > > @PersistenceContext and @PersistenceUnit annotations can also be used on > method and class level. > On method level the annotation could be put on a setter. > On class level I am not sure how we would interpret it. I have not found any > good real life example for this so I propose to not support it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Aries Asynchronous OSGi Services 1.0.0
Hi, So the good news is that the release versions all pass the relevant compliance tests for their respective specifications, but I have noted two issues… I’m unable to build from source unless I re-version all of the bundles to 1.0.0-SNAPSHOT and do a mvn clean install first. If I fail to do this then the version checker fails the build. Once I have 1.0.0-SNAPSHOT versions in my local repository then everything works fine. The RAT check fails because the source files are missing Apache licence headers (my fault originally). This applies to the Promise API implementation and the Async API and Async Impl bundles. I’m not sure what the policy is for licence headers on the classes/interfaces in the org.osgi.xxx namespace. In summary, I’m +1 for the binaries, which work and contain all of the necessary licence info. I’m not sure if we need to respin for the source/build issues though. Regards, Tim > On 3 Jul 2015, at 16:42, Sergey Beryozkin wrote: > > +1 > Sergey > On 03/07/15 12:55, dav...@apache.org wrote: >> Here's my +1 >> >> David >> >> On 3 July 2015 at 11:36, wrote: >>> Hi all, >>> >>> I'm calling a vote on the first release of the Aries Asynchronous OSGi >>> Services implementation. This implements the OSGi Asynchronous >>> Services specification (chapter 138) and the OSGi Promises >>> specification (chapter 705) of the upcoming OSGi Enterprise R6 >>> specifications, which are available as proposed final draft [1]. >>> >>> Staging repository: >>> https://repository.apache.org/content/repositories/orgapachearies-1031 >>> >>> For details on getting started see >>> http://aries.apache.org/modules/async-svcs.html >>> Kudos to Tim Ward for providing this implementation. >>> >>> Please vote: >>> >>> +1 Approve the release >>> -1 Do not approve the release (please explain why) >>> >>> This vote will be open for at least 72 hours. >>> >>> Best regards, >>> >>> David Bosschaert >>> >>> [1] http://www.osgi.org/Specifications/Drafts >
[jira] [Resolved] (ARIES-1344) Support multiple EntityManager injections per class
[ https://issues.apache.org/jira/browse/ARIES-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giuseppe Gerla resolved ARIES-1344. --- Resolution: Fixed > Support multiple EntityManager injections per class > --- > > Key: ARIES-1344 > URL: https://issues.apache.org/jira/browse/ARIES-1344 > Project: Aries > Issue Type: Improvement > Components: JPA >Affects Versions: jpa-2.0.0 >Reporter: Christian Schneider >Assignee: Giuseppe Gerla > Fix For: jpa-2.1.0 > > > Currently only the first @PersistenceContext or @PersistenceUnit annotation > is injected. > A class may contain more than one inject though. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ARIES-1344) Support multiple EntityManager injections per class
[ https://issues.apache.org/jira/browse/ARIES-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giuseppe Gerla reassigned ARIES-1344: - Assignee: Giuseppe Gerla > Support multiple EntityManager injections per class > --- > > Key: ARIES-1344 > URL: https://issues.apache.org/jira/browse/ARIES-1344 > Project: Aries > Issue Type: Improvement > Components: JPA >Affects Versions: jpa-2.0.0 >Reporter: Christian Schneider >Assignee: Giuseppe Gerla > Fix For: jpa-2.1.0 > > > Currently only the first @PersistenceContext or @PersistenceUnit annotation > is injected. > A class may contain more than one inject though. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Aries Asynchronous OSGi Services 1.0.0
+1 Sergey On 03/07/15 12:55, dav...@apache.org wrote: Here's my +1 David On 3 July 2015 at 11:36, wrote: Hi all, I'm calling a vote on the first release of the Aries Asynchronous OSGi Services implementation. This implements the OSGi Asynchronous Services specification (chapter 138) and the OSGi Promises specification (chapter 705) of the upcoming OSGi Enterprise R6 specifications, which are available as proposed final draft [1]. Staging repository: https://repository.apache.org/content/repositories/orgapachearies-1031 For details on getting started see http://aries.apache.org/modules/async-svcs.html Kudos to Tim Ward for providing this implementation. Please vote: +1 Approve the release -1 Do not approve the release (please explain why) This vote will be open for at least 72 hours. Best regards, David Bosschaert [1] http://www.osgi.org/Specifications/Drafts
Re: [VOTE] Release Aries Asynchronous OSGi Services 1.0.0
Here's my +1 David On 3 July 2015 at 11:36, wrote: > Hi all, > > I'm calling a vote on the first release of the Aries Asynchronous OSGi > Services implementation. This implements the OSGi Asynchronous > Services specification (chapter 138) and the OSGi Promises > specification (chapter 705) of the upcoming OSGi Enterprise R6 > specifications, which are available as proposed final draft [1]. > > Staging repository: > https://repository.apache.org/content/repositories/orgapachearies-1031 > > For details on getting started see > http://aries.apache.org/modules/async-svcs.html > Kudos to Tim Ward for providing this implementation. > > Please vote: > > +1 Approve the release > -1 Do not approve the release (please explain why) > > This vote will be open for at least 72 hours. > > Best regards, > > David Bosschaert > > [1] http://www.osgi.org/Specifications/Drafts
[VOTE] Release Aries Asynchronous OSGi Services 1.0.0
Hi all, I'm calling a vote on the first release of the Aries Asynchronous OSGi Services implementation. This implements the OSGi Asynchronous Services specification (chapter 138) and the OSGi Promises specification (chapter 705) of the upcoming OSGi Enterprise R6 specifications, which are available as proposed final draft [1]. Staging repository: https://repository.apache.org/content/repositories/orgapachearies-1031 For details on getting started see http://aries.apache.org/modules/async-svcs.html Kudos to Tim Ward for providing this implementation. Please vote: +1 Approve the release -1 Do not approve the release (please explain why) This vote will be open for at least 72 hours. Best regards, David Bosschaert [1] http://www.osgi.org/Specifications/Drafts
Re: [VOTE] Release Aries Subsystems 2.0.2
With 6 +1s this vote passes. I've promoted the artifacts in Maven central and will update http://aries.apache.org/modules/subsystems.html I've also updated https://en.wikipedia.org/wiki/OSGi_Specification_Implementations to mention that this implementation implements Subsystems 1.1. David On 2 July 2015 at 08:47, wrote: > Here's my +1 > > David > > On 30 June 2015 at 08:24, wrote: >> Hi, >> >> Subsystems 2.0.1 was released yesterday, but it contained a serious >> bug which made it not usable with the Felix Bundle Repository >> implementation. Therefore I'm calling a vote on Subsystems 2.0.2, >> which has this issue resolved. >> >> The following modules are part of this release: >> subsystem-api 2.0.2 >> subsystem-core 2.0.2 >> subsystem-bundle 2.0.2 >> >> The following bug was fixed since Subsystems 2.0.1: >> ARIES-1339 - IllegalAccessException when installing a new subsystem >> >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachearies-1029 >> >> More information about Aries Subsystems: >> http://aries.apache.org/modules/subsystems.html >> >> Please vote: >> >> +1 Approve the release >> -1 Do not approve the release (please explain why) >> >> This vote will be open for at least 72 hours. >> >> Best regards, >> >> David Bosschaert
Re: [VOTE] Release Transaction Manager 1.2.1
+1 David On 3 July 2015 at 08:57, Guillaume Nodet wrote: > I've staged a release of Transaction Manager 1.2.1 for vote. > The only change is an upgrade to Geronimo Transaction Manager 3.1.3 which > fixes GERONIMO-6543 (Geronimo XA transaction recovery not working for > heuristically completed transactions). > > Staging repository: > https://repository.apache.org/content/repositories/orgapachearies-1030 > > Please review and vote: > >[ ] +1 Release Transaction Manager 1.2.1 >[ ] -1 Do not > > Thx ! > Guillaume Nodet
[jira] [Commented] (ARIES-1333) Cannot instantiate singleton collections in blueprint
[
https://issues.apache.org/jira/browse/ARIES-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613011#comment-14613011
]
Guillaume Nodet commented on ARIES-1333:
The problem is caused by generics.
The collections generated from the xml are not typed, so they are effectively
ArrayList, HashSet and HashMap.
However, the constructor expects List, Set and Map, and those are not compatible (at least from a blueprint POV), so there
is a conversion between the untyped arguments to the real typed constructor
arguments.
If you remove the generics from the ReferringBean, you'll see that the same
instances are passed.
> Cannot instantiate singleton collections in blueprint
> -
>
> Key: ARIES-1333
> URL: https://issues.apache.org/jira/browse/ARIES-1333
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
>Affects Versions: blueprint-core-1.4.2
>Reporter: Tomas Rohovsky
> Attachments: bean-reference.zip
>
>
> New instances of collections (set, list, map) are always created when
> referring them by different beans. So, it behaves like the {{prototype}}
> scope would be set on them. The {{singleton}} scope should be default, but it
> doesn't work even if it is set explicitly. A Camel based reproducer is
> attached. Note that this is not an issue for Spring configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Release Transaction Manager 1.2.1
+1 Here is the jira corresponding jira version https://issues.apache.org/jira/browse/ARIES/fixforversion/12332959 Christian On 03.07.2015 09:57, Guillaume Nodet wrote: I've staged a release of Transaction Manager 1.2.1 for vote. The only change is an upgrade to Geronimo Transaction Manager 3.1.3 which fixes GERONIMO-6543 (Geronimo XA transaction recovery not working for heuristically completed transactions). Staging repository: https://repository.apache.org/content/repositories/orgapachearies-1030 Please review and vote: [ ] +1 Release Transaction Manager 1.2.1 [ ] -1 Do not Thx ! Guillaume Nodet -- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com
[jira] [Resolved] (ARIES-1340) Upgrade to geronimo transaction manager 3.1.3
[ https://issues.apache.org/jira/browse/ARIES-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved ARIES-1340. Resolution: Fixed https://github.com/apache/aries/commit/6dc9dc638e555e8417c8ae059ec5dd223915692d > Upgrade to geronimo transaction manager 3.1.3 > - > > Key: ARIES-1340 > URL: https://issues.apache.org/jira/browse/ARIES-1340 > Project: Aries > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: transaction-manager-1.2.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] Release Transaction Manager 1.2.1
I've staged a release of Transaction Manager 1.2.1 for vote. The only change is an upgrade to Geronimo Transaction Manager 3.1.3 which fixes GERONIMO-6543 (Geronimo XA transaction recovery not working for heuristically completed transactions). Staging repository: https://repository.apache.org/content/repositories/orgapachearies-1030 Please review and vote: [ ] +1 Release Transaction Manager 1.2.1 [ ] -1 Do not Thx ! Guillaume Nodet
