> I’m not sure if my suggestion would continue to work i R7 due to coordination
> support.
Sorry, expand please?
-
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail:
I’m not sure if my suggestion would continue to work i R7 due to coordination
support.
david jencks
> On Jan 9, 2017, at 11:46 AM, David Jencks wrote:
>
> Felix DS runs off the configuration events too, so just waiting for the
> events isn’t going to determine
Pouwelse [mailto:b...@pouwelse.com]
Sent: 09 January 2017 21:20
To: users@felix.apache.org
Subject: Re: Config admin: when do the CM_UPDATED, CM_DELETED events actually
get called?
Hi Tom,
Let me start with saying that I'm not sure if the approach works with DS
components but we use Amdatu Testing
Hi Tom,
Let me start with saying that I'm not sure if the approach works with DS
components but we use Amdatu Testing for our tests, that has an option for
synchronous delivery of configurations [1]. This synchronous delivery mode
bypasses ConfigAdmin and applies configuration changes directly to
Felix DS runs off the configuration events too, so just waiting for the events
isn’t going to determine whether you or DS is notified first.
I’m not sure if you can use serviceRanking to determine which configuration
listener gets notified first. If you can arrange that your listener is called
I'm trying to use the CM_UPDATED and CM_DELETED config admin events in a test
harness to ensure that a configuration change has been actioned before the test
case gets run, but I'm unclear when exactly these get called.
The OSGi specification doesn't seem very enlightening. "An event is fired
6 matches
Mail list logo