Hi Peter, if I understand correctly (I must admit it's not immediately clear to me), you think of Aggregate State service as something that should be a general purpose service provided by OSGi implementation or some library. In another words, it's not something that developers need to implement themselves in each project. Is that right? If so, I do believe it will be very useful addition to the OSGi specs. I would also love to see it provided as independent nonstandard library meanwhile!
That said, I think it would be very useful if the article can give (or point to) an example of how a service can modify its own service properties! I don't think this is a well understood concept among OSGi developers (much like the negative conditions you mentioned). Perhaps many developers could benefit from it if they were aware of the possibilities! Best regards, Mien On Mon, Apr 24, 2017 at 7:12 PM, Peter Kriens <peter.kri...@aqute.biz> wrote: > I’ve written a blog about start ordering issues in OSGi and a potential > solution. This likely will interest many since it is a vexing OSGi problem. > > Feedback appreciated. > > http://aqute.biz/2017/04/24/aggregate-state.html > > Kind regards, > > Peter Kriens > > -- http://about.me/milen
