[jboss-jira] [JBoss JIRA] (AS7-5201) 128.3.8 Stopping the Web Application Bundle

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Tue Dec 11 15:31:17 EST 2012


    [ https://issues.jboss.org/browse/AS7-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740723#comment-12740723 ] 

Thomas Diesler edited comment on AS7-5201 at 12/11/12 3:30 PM:
---------------------------------------------------------------

This could work such that the trigger for the deferred module phase proactively checks for a duplicate context path and does not actually trigger the module phase and everything after, but throws a BundleException instead. The stop lifecycle change of the active wab must remove the WebContextService (instead of just stopping it) and trigger the deferred module phase for the first bundle waiting in the collision queue.
                
      was (Author: thomas.diesler):
    Depends on AS7-5653
                  
> 128.3.8 Stopping the Web Application Bundle
> -------------------------------------------
>
>                 Key: AS7-5201
>                 URL: https://issues.jboss.org/browse/AS7-5201
>             Project: Application Server 7
>          Issue Type: Sub-task
>          Components: OSGi
>            Reporter: David Bosschaert
>             Fix For: 7.2.0.CR1
>
>
> It is possible that there are one or more colliding WABs because they had the same Context Path as this stopped WAB. If such colliding WABs exists then the Web Extender must attempt to deploy the colliding WAB with the lowest bundle id.

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


More information about the jboss-jira mailing list