You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Rice Yeh <ri...@gmail.com> on 2011/01/03 04:04:58 UTC
the life cycle of a bundle without Activator
Hi,
Is it right that a bundle without Activator has only states INSTALLED,
RESOLVED, AND UNINSTALLED? That is, it will never be activated since it has
no activator.
Rice
Re: the life cycle of a bundle without Activator
Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 1/2/11 22:04, Rice Yeh wrote:
> Hi,
> Is it right that a bundle without Activator has only states INSTALLED,
> RESOLVED, AND UNINSTALLED? That is, it will never be activated since it has
> no activator.
It can be activated, but that won't have any impact other than changing
its stated from RESOLVED to ACTIVE. If the bundle is just a library,
then there is no need to ever activate it.
If the bundle is involved in some sort of extender pattern where it
implements an extension, then it is possible that the extender is using
the ACTIVE state as a trigger to do something on behalf of the
activator-less bundle. In such a case, activating the bundle is
necessary, even though it doesn't have an activator. You can see this
with bundles for Declarative Services or iPOJO, for example.
-> richard
> Rice
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org