I think that regarding interactivity (like progress) and user feedback, EventAdmin should be a good solution (currently). At some point push streams may be a good option too.
FrameworkEvents are more or less "for the framework". What you've whiteness is a condition in a component which is not part of the actual framework. Lastly, if your component can possibly barf on bad configuration, I'd say that the component could be made more robust. 1) using metatype you can create a schema which a UI can adhere user input to avoiding bad configuration 2) the component should protect itself where input is loosely typed just like any other code should. 3) logging should probably also be added for debugging purposes Lastly, maybe you're device needs a "diagnostic" app which dumps the logs over a network connection like HTTP when requested. One thing I've really longed for is metatype to assert that configurations satisfy the schema however the configuration was created, not only when called upon to do so manually. Sincerely, - Ray On Wed, Oct 19, 2016 at 8:17 AM, Benson Margulies <bimargul...@gmail.com> wrote: > 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 > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
