[jboss-osgi-issues] [JBoss JIRA] Resolved: (JBOSGI-148) Autostart bundles when deployed in JBossAS

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBOSGI-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBOSGI-148.
-----------------------------------

    Resolution: Done


Done



> Autostart bundles when deployed in JBossAS
> ------------------------------------------
>
>                 Key: JBOSGI-148
>                 URL: https://jira.jboss.org/jira/browse/JBOSGI-148
>             Project: JBoss OSGi
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Integration (JBoss)
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: Framework 1.0.0 Alpha1
>
>         Attachments: jbosgi142-bundleA.jar, jbosgi142-bundleX.jar
>
>
> The basic issue is that a bundle deployment when put in 
> OSGiBundleStateDeployer
>     requiredStage = DeploymentStages.DESCRIBE
> it will only progress to Bundle.INSTALLED, hence the bundle with not resolve nor start.
> When requiredStage = DeploymentStages.CLASSLOADER or above, the bundle can start when all its dependencies are resolved.
> The bundle deployment will however fail. if it has unresolved dependencies.
> The desired behaviour is:
> Bundles with unresolved dependencies get INSTALLED without error.
> Bundles with resolved dependencies get STARTED without error.
> A bundle that could only get INSTALLED (but not RESOLVED) gets STARTED when it's dependencies can be RESOLVED.

-- 
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