[jboss-jira] [JBoss JIRA] Updated: (JBAS-9366) OSGi bundles dropped in standalone/deployments do not get started any more

[Thomas Diesler (JIRA)]

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

Thomas Diesler updated JBAS-9366:
---------------------------------

    Fix Version/s: 7.0.0.Beta4


BundleInstallService has a dependency on ServiceNames.FRAMEWORK_INIT

This causes the Framework to get initialized, but not started on first bundle deployment - this is a bug.

Note however, starting bundle on hot deployment is not as trivial as it seems because the notion of "deployment set" is not defined. The correct behaviour would be 

b1.install
b2.install
...
bn.install

b1-bn.start

See JBAS-8517



> OSGi bundles dropped in standalone/deployments do not get started any more
> --------------------------------------------------------------------------
>
>                 Key: JBAS-9366
>                 URL: https://issues.jboss.org/browse/JBAS-9366
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: OSGi integration
>    Affects Versions: 7.0.0.Beta3
>            Reporter: David Bosschaert
>            Assignee: Thomas Diesler
>             Fix For: 7.0.0.Beta4
>
>
> Up until Beta2 OSGi bundles dropped in the standalone/deployments folder were started automatically. This is pretty important for people getting started with the system.
> Since Beta3 this doesn't happen any more. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira