[jboss-jira] [JBoss JIRA] (WFLY-1641) Complete support for Bundle uninstall

[Thomas Diesler (JIRA)]

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

Thomas Diesler moved JBOSGI-705 to WFLY-1641:
---------------------------------------------

    Workflow: GIT Pull Request workflow   (was: jira)
     Project: WildFly  (was: JBoss OSGi)
         Key: WFLY-1641  (was: JBOSGI-705)

    
> Complete support for Bundle uninstall
> -------------------------------------
>
>                 Key: WFLY-1641
>                 URL: https://issues.jboss.org/browse/WFLY-1641
>             Project: WildFly
>          Issue Type: Sub-task
>            Reporter: Thomas Diesler
>
> Bundle uninstall only removes the BundleRevision from the runtime if it is no longer in use. The classloader associated with an uninstalled bundle that is still in use remains active.
> Approach #1 -  "in use" semantic specific to Bundle deployments
> An undeploy management operation undeploys the bundle revision but holds in the MODULE phase when the revision is still in use
> This is similar to deferred MODULE phase for deploy operation
> in use is not respected for non-osgi deployments and hence breaks bundle deployments that depend on them
> Approach #2 -  "in use" semantic applies to all deployment types
> Undeploy will only destroy the Module service if the Module is not in use by another deployment
> When Module usage drops to zero, undeploy continues and removes the deployment from management 
> This approach would map cleanly - there is no cascading destroy effect. i.e. when you undeploy a jar that a webapp depends on
> Services provided by the undeployed deployment would always go down, only classloader destruction is deferred

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira