Not in R6. Under discussion for R7 is a service property for the ServiceComponentRuntime service which would hold a change count for the DTO set. Then whenever the DTO set changes, the service properties for the ServiceComponentRuntime service would change. So you could listen for MODIFIED service events on the ServiceComponentRuntime service if you need to track changes to the DTO set.
We also look to use the same service property for HttpServiceRuntime and JaxRSServiceRuntime for the same reason.
--
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
hargr...@us.ibm.com
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
hargr...@us.ibm.com
----- Original message -----
From: Scott Lewis <sle...@composent.com>
Sent by: osgi-dev-boun...@mail.osgi.org
To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
Cc:
Subject: [osgi-dev] ServiceComponentRuntime service
Date: Sun, Feb 12, 2017 4:34 PM
In R6 chap 112 there is the
org.osgi.service.component.runtime.ServiceComponentRuntime service that
exposes (e.g) getComponentDescriptionDTO,
enableComponent/disableComponent, etc. One thing that does not seem to
be present, however, is any sort of listener/event structure for
responding to component changes.
An example of what I mean by such a listener/event structure exists in
the RemoteServiceAdminListener and RemoteServiceAdminEvent (and with
EventAdmin for async).
Is there some other pattern for (e.g.) SCR tooling to respond to such
runtime changes?
Thanks,
Scott
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
