I've found myself in situations where a (user) configuration error leads to a throw in a DS @Activate method, and the eventual result is that a component doesn't start and a service isn't found. While the activate message can certainly log, it would be better, in my view, if I could come up with a strategy for a more direct notification.
Would readers here recommend EventAdmin for this job, or is there some way to generate events at the framework level? One complexity is that this is an 'embedded' application; the eventual audience of the situation is code that starts up the framework, not code inside the framework. _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
