Hi, got another question regarding Declarative Services. Is there anyway for a component to provide an interface which is NOT published to the service registry before the component is activated? Let's say I have a component which provides, among other things, some kind of an event handler, however, the very fact that events are generated should not cause the component to be activated, but should only be registered in the service registry whenever the SCR activates the component (i.e. when one of the 'other things' is requested).
I realize that this is of course possible by registering the services upon activation (and unregistering on deactivation), I also realize that this is probably the best solution when considering race conditions. I am, however, currently more concerned with if it's possible without referencing OSGi classes to any larger extent in the code. Is this be possible? Eventing when the component is activated/deactivated and letting another component do the work would probably also do the trick, however, I found no reference to any events in those situations, did I miss something? Greetings, Fredrik. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
