I think I understand the use-case now as well. The osgi-dev thread
started by Christian [1] also provides valuable insight.
If I can summarize the quiesce functionality it is aimed at preventing
operations from failing. Rather than failing, you stop accepting
requests, then perform some interruptiv
Hi Christian
I think you are doing a good work.
In the past, I send an email about some JPA issue that from my point of
view are old. I report the list below:
1. ARIES-735 (I don't think that aries-jpa implements OSGi JPA
specification)
2. ARIES-736 (same before)
3. ARIES-741 (Could be already imp
[
https://issues.apache.org/jira/browse/ARIES-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved ARIES-1297.
Resolution: Won't Fix
Fix Version/s: (was: jpa-container-context-1.0.5)
Please excuse the mail flood about changed issues.
I am currently trying to cleanup the jira versions a bit.
So what I am try to achieve is to reflect all released versions with
their release date and make sure they do not have open issues.
I added a release date for versions that were already
[
https://issues.apache.org/jira/browse/ARIES-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-596:
--
Fix Version/s: (was: 0.4)
> Bank sample fails - proxy problem?
>
[
https://issues.apache.org/jira/browse/ARIES-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-566:
--
Fix Version/s: (was: 0.4)
> NPE when generating bundle repository for invalid bundle
[
https://issues.apache.org/jira/browse/ARIES-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-839:
--
Fix Version/s: (was: 0.4)
> Aries JMX whiteboard should support MXBeans
> ---
[
https://issues.apache.org/jira/browse/ARIES-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-1173:
---
Fix Version/s: (was: 0.4)
> 'No persistence descriptors' message confuses more peo
[
https://issues.apache.org/jira/browse/ARIES-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-570:
--
Fix Version/s: (was: 0.4)
> Blog itests failure -
> org.apache.aries.samples.blog.it
[
https://issues.apache.org/jira/browse/ARIES-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-595:
--
Fix Version/s: (was: 0.4)
> unravelled bank sample
> --
>
>
Many thanks for the explanations.
For JPA I think I now understand what we need to achieve. As soon as a
persistence unit bundle is quiesced no new EMs should be created.
The opened EMs of the persistence bundle are closed when all calls that
use them are finished. Then when all those EMs are c
On 13.02.2015 17:40, David Jencks wrote:
I don't know what the quiesce service is supposed to do either. However I take
issue with one statement below… hopefully I misunderstood what you mean:
- bundleA stops which should not affect inflight processing inside bundle A
Lets supp
I've been digging around in my memory. The Quiesce capability is a like a
soft-stop. It's a generic capability that is enforced differently depending
on the context. It's more normal for an extender to implement the
QuiesceParticipant rather than an individual bundle. In the case of the
Blueprint e
I don't know what the quiesce service is supposed to do either. However I take
issue with one statement below… hopefully I misunderstood what you mean:
> - bundleA stops which should not affect inflight processing inside bundle A
Lets suppose A's services are implemented as DS com
I've just sent the board report for February. Next report is due 8th April.
-- Forwarded message --
From: Jeremy Hughes
Date: 13 February 2015 at 14:30
Subject: Apache Aries board report Feb 2015
To: ASF Board
Here is our report:
# February 2015 Board report
Apache Aries deli
On 13.02.2015 12:43, Guillaume Nodet wrote:
2015-02-13 12:23 GMT+01:00 Christian Schneider :
On 13.02.2015 11:58, Guillaume Nodet wrote:
Your example expects a simple restart of the service, I'm talking about an
update/refresh of the bundle.
But even restarting the service, if the service is
2015-02-13 12:23 GMT+01:00 Christian Schneider :
> On 13.02.2015 11:58, Guillaume Nodet wrote:
>
>>
>>
>> Your example expects a simple restart of the service, I'm talking about an
>> update/refresh of the bundle.
>> But even restarting the service, if the service is an EntityManager, that
>> does
On 13.02.2015 11:58, Guillaume Nodet wrote:
Your example expects a simple restart of the service, I'm talking about an
update/refresh of the bundle.
But even restarting the service, if the service is an EntityManager, that
does not work afaik : you can't just switch it in the middle of your
pro
[
https://issues.apache.org/jira/browse/ARIES-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319958#comment-14319958
]
Christian Schneider commented on ARIES-1270:
I found that restarting the hiber
2015-02-13 11:17 GMT+01:00 Christian Schneider :
> On 13.02.2015 10:43, Guillaume Nodet wrote:
>
>>
>>
>> I think you did not understand the concept of *clean* shutdown which I'm
>> trying to explain.
>> I think there's a big difference between reacting to the fact that the
>> database connection
On 13.02.2015 10:43, Guillaume Nodet wrote:
I think you did not understand the concept of *clean* shutdown which I'm
trying to explain.
I think there's a big difference between reacting to the fact that the
database connection has been lost, which is out of your control and the
only thing you c
2015-02-13 9:04 GMT+01:00 Christian Schneider :
> On 12.02.2015 21:41, Guillaume Nodet wrote:
>
>> Quiescing a single bundle does not make sense I think. Quiescing
>> obviously means you want to stop a bunch of bundles. In this case, if you
>> want to actually stop bundle A, you also need to stop
[
https://issues.apache.org/jira/browse/ARIES-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319786#comment-14319786
]
Christian Schneider commented on ARIES-628:
---
I agree that supporting annotation f
[
https://issues.apache.org/jira/browse/ARIES-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-1079:
---
Affects Version/s: jpa-blueprint-aries-1.0.4
> The jpa.xsd incorrectly specifies bp:ma
[
https://issues.apache.org/jira/browse/ARIES-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved ARIES-1079.
Resolution: Fixed
Fix Version/s: jpa-blueprint-aries-1.0.5
Assignee:
[
https://issues.apache.org/jira/browse/ARIES-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved ARIES-1023.
Resolution: Fixed
Fix Version/s: jpa-blueprint-aries-1.0.5
Assignee:
[
https://issues.apache.org/jira/browse/ARIES-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated ARIES-1023:
---
Affects Version/s: jpa-blueprint-aries-1.0.4
> Construct a persistence unit with param
On 12.02.2015 21:41, Guillaume Nodet wrote:
Quiescing a single bundle does not make sense I think. Quiescing
obviously means you want to stop a bunch of bundles. In this case, if
you want to actually stop bundle A, you also need to stop all bundles
using services from A, so that would include B
28 matches
Mail list logo
