[jboss-osgi-issues] [JBoss JIRA] Commented: (JBOSGI-210) Bundle is only installed but not started.
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Wed Nov 25 05:33:29 EST 2009
[ https://jira.jboss.org/jira/browse/JBOSGI-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12496506#action_12496506 ]
Thomas Diesler commented on JBOSGI-210:
---------------------------------------
4.4.6.1 Activation Policies
The activation of a bundle can also be deferred to a later time from its start
using an activation policy. This policy is specified in the Bundle-
ActivationPolicy header with the following syntax:
Bundle-ActivationPolicy ::= policy ( ';' directive )*
policy ::= 'lazy'
The only policy defined is the lazy activation policy. If no Bundle-Activa-
tionPolicy header is specified, the bundle will use eager activation.
> Bundle is only installed but not started.
> -----------------------------------------
>
> Key: JBOSGI-210
> URL: https://jira.jboss.org/jira/browse/JBOSGI-210
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Integration (Equinox)
> Affects Versions: JBossOSGi 1.0.0 Beta4
> Environment: OS: WinXP SP3 & CygWin V1.7 /run.sh had to be changed to work: JAVA_OPTS must be set AFTER all cygpath commands/
> Reporter: Csaba Szucs
> Attachments: console.log, JBossOSGiTest_1.0.0.200911251029.jar
>
>
> My sample hot-deployed bundle is only installed but not started by the framework.
> This same bundle is also started within JBoss OSGi with Apache Felix integration.
> My sample bundle was created by Eclipse V3.5 as an Equinox plug-in and contains an Activator class only with code to log the bundle's lifecycle events.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-osgi-issues
mailing list