|
|
|
|
|
|
|
|
|
DS & Lazy Avctivation (was: Re: Eclipse RCP with OSGi Service) [message #827332 is a reply to message #826749] |
Fri, 23 March 2012 07:11 |
|
Hi,
Am 22.03.2012 14:05, schrieb Tom Schindl:
> I don't think this is fully correct - lazy activation is REQUIRED when
> you use DS
DS in Equinox works as any other thing in OSGi. It's only fully
functional once any involved bundle (the DS implementation, the DS
provider as well as the DS consumer) is ACTIVE. Until that point it's
not fully functional. For example, it may discover your components and
the components may be fully satisfiable but they are not activated
because the DS framework does not load the component class because the
bundle is not ACTIVE. (*[1]) Here is when Bundle-ActivationPolicy: lazy
comes into play. It allows the DS framework to auto-start the bundle in
order to load the component class.
[1]: Note, in OSGi classes from a RESOLVED bundle can be loaded. Thus, I
think its the DS implementation that puts the additional ACTIVE
constraint onto that model.
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxx
http://wagenknecht.org/
|
|
|
Powered by
FUDForum. Page generated in 0.04166 seconds