[jboss-jira] [JBoss JIRA] (AS7-4486) Remove feature that starts bundles automatically on 'deploy' operation

[Thomas Diesler (JIRA)]

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

Thomas Diesler updated AS7-4486:
--------------------------------

    Fix Version/s: 7.1.2.Final-redhat1
                       (was: 7.2.0.Alpha1)

    
> Remove feature that starts bundles automatically on 'deploy' operation 
> -----------------------------------------------------------------------
>
>                 Key: AS7-4486
>                 URL: https://issues.jboss.org/browse/AS7-4486
>             Project: Application Server 7
>          Issue Type: Task
>          Components: OSGi
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: 7.1.2.Final-redhat1
>
>
> Historically we attempt to start an OSGi bundle that gets deployed through the management interface. This however is error prone when a larger set of bundles is deployed and may lead to a deploym,ent ordering issue.
> Now that we have OSGi runtime operations for start/stop in place bundles should only reach INSTALLED state when deployed through the management interface. An explicit start/stop operation should be required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira