On Wed, Oct 19, 2016 at 8:12 AM, Peter Kriens <peter.kri...@aqute.biz> wrote: > Not sure. This is the purpose of the log? If you’re interested in a more > active notification then just listen to the log events (LogReaderService) and > send to console out or whatever. Showing all errors is very useful for > debugging.
The log is not terrible, don't get me wrong. The shape I'm thinking of us this: - Customer application calls startup API. - Startup API starts up container - 'Something goes wrong'. - a FrameworkEvent of type ERROR shows up - Customer sees focussed error like 'license file missing' - log is there for more subtle/hard to anticipate situations If I am not allowed to generate FrameworkEvents, I could plugin in EventAdmin; but I was concerned that (a) people here would write 'oh, that's old and disliked', and (b) that it will be a bit clumsy to arrange for the results to show up 'outside'. But, on consideration, I see how to do that not too badly. > > Kind regards, > > Peter Kriens > >> On 19 okt. 2016, at 14:11, Benson Margulies <bimargul...@gmail.com> wrote: >> >> 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 > > > _______________________________________________ > 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
