Jan Willem Janssen wrote
> 
>> On 10 Nov 2016, at 16:18, Carsten Ziegeler <[email protected]> wrote:
>>
>> Let's assume you have an app, consisting of dozens of services, for
>> simplicity let's assume they are all in one bundle. Now you don't want
>> to start any of these services until some condition is met.
>> Clearly, you can add these special reference to each and every of the
>> dozen services, but that doesn't look nice to me.
> 
> Given that they all reside in the same bundle makes it quite easy to let
> all services act upon a bundle-local service that acts as a gatekeeper for
> starting up the other services. It makes it quite explicit when things do
> not start up as to why this happens.
> 
> Using the module layer to solve this problem sounds still like a wrong
> approach to me.
> 

I know that my bundle does not work at all if lets say a database is not
available. However in my app I don't need a dependency on any database
service as my services are picked up using whiteboard.

I don't see any reason to start my bundle at all.

 Carsten

-- 
Carsten Ziegeler
Adobe Research Switzerland
[email protected]


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to