[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Regarding Lazy Activation


Do not do this. It is a common newbie mistake: there should be no
start-ordering dependency between bundles.

You do not state *why* you want B to start after A has started. I
assume that you want to publish a service from A and consume it from
B? The correct way to do this is have B *listen* for the availability
of the service it needs to use, then A and B can be started in any

As Petar points out, using Declarative Services (DS) is a much easier
way to implement services, since it takes care of all the aspects of
listening for availability etc. I strongly recommend that you use DS
instead of coding against the low-level OSGi services APIs.


On Wed, Feb 16, 2011 at 1:36 PM, ajinkya prabhune
<ajinkya.prabhune@xxxxxxxxx> wrote:
> Hello,
> I am quite new to the concept of OSGi and bundles.
> I have this issue.
> For eg - I have 2 bundles
> Bundle A and Bundle B, Bundle A depends on Bundle B
> But I want to start Bundle B only when Bundle A is started...
> what are the ways to do it ? I manually found out the Bundle B using the
> Bundle object and started the Bundle B with bundle.start() but I
> would like to do it without the Java Code. can the Framework Help me.
> I am not sure but how does Bundle ActivationPolicy lazy works ?
> Thank u and regards
> --
> Thank you and Regards
> Ajinkya Prabhune
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev