[
https://issues.apache.org/jira/browse/DIRAPI-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183983#comment-15183983
]
Stefan Seelmann edited comment on DIRAPI-273 at 3/7/16 11:41 PM:
-----------------------------------------------------------------
Eclipse/Equinox doesn't start any bundle automatically. Only if
"Bundle-ActivationPolicy: lazy" (or the older "Eclipse-LazyStart: true") is
declared Equinox starts them at all, and then also only if some class of that
bundle is loaded. Without the "Bundle-ActivationPolicy: lazy" we need to start
the bundles ourselves, either programatically or within .product file or
config.ini. But the latter would only work for the RCP application, not when
installing the Studio plugins within an existing Eclipse. So the
programatically start of the bundles is the way to go.
Two useful links that show that Eclipse behaves different than other OSGi envs::
* https://wiki.eclipse.org/Lazy_Start_Bundles
*
https://stackoverflow.com/questions/17590464/lazy-activation-of-eclipse-plugins/17592449#17592449
was (Author: seelmann):
Eclipse/Equinox doesn't start any bundle automatically. Only if
"Bundle-ActivationPolicy: lazy" (or the older "Eclipse-LazyStart: true")
Equinox starts them at all, and then also only if some class of that bundle is
loaded. Without the "Bundle-ActivationPolicy: lazy" we need to start the
bundles ourselves.
Two useful links that show that Eclipse behaves different than other OSGi envs::
* https://wiki.eclipse.org/Lazy_Start_Bundles
*
https://stackoverflow.com/questions/17590464/lazy-activation-of-eclipse-plugins/17592449#17592449
> api-ldap-net-mina bundle remains in STARTING mode
> -------------------------------------------------
>
> Key: DIRAPI-273
> URL: https://issues.apache.org/jira/browse/DIRAPI-273
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 1.0.0-M33
> Environment: Linux; Felix
> Reporter: Ivo Leitão
> Labels: Felix, OSGI
>
> After deploying the api-ldap-net-mina bundle in an OSGI environment (in my
> case the Felix container) the bundle remains in STARTING mode til an explicit
> stop and start via a gogo shell command or via Felix webconsole. I've found
> that removing Bundle-ActivationPolicy: lazy in the MANIFEST.MF resolves this
> issues. From what I've investigated is not a good pratice to use
> Bundle-ActivationPolicy at least in a Felix environment (I know that is more
> common in Equinox). It's possibile to remove this without affecting other
> OSGI platforms.
> What I can say is that it does not work OOB with this directive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
