[jboss-jira] [JBoss JIRA] (AS7-3585) Allign deployment phases with OSGi terminology

[Thomas Diesler (JIRA)]

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

Thomas Diesler commented on AS7-3585:
-------------------------------------

I propose the following mapping

{code}
STRUCTURE         =>   STRUCTURE

PARSE             =>   PRE_INSTALL
REGISTER          =>   INSTALL
                  =>   POST_INSTALL

DEPENDENCIES      =>   PRE_RESOLVE
CONFIGURE_MODULE  =>   RESOLVE
FIRST_MODULE_USE  =>   POST_RESOLVE

POST_MODULE       =>   PRE_ACTIVATE
INSTALL           =>   ACTIVATE
                  =>   POST_ACTIVATE

CLEANUP           =>   CLEANUP
{code}
                
> Allign deployment phases with OSGi terminology
> ----------------------------------------------
>
>                 Key: AS7-3585
>                 URL: https://issues.jboss.org/browse/AS7-3585
>             Project: Application Server 7
>          Issue Type: Task
>          Components: OSGi, Server
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: 7.2.0.CR1
>
>
> In OSGi we have
> * INSTALLED
> * RESOLVED
> * ACTIVE
> * UNINSTALLED
> It'd be useful to talk about modules and osgi bundles in the same jagon - i.e
> If a deployment is INSTALLED it has valid metadata
> If a deployment is RESOLVED it has Module/ClassLoader associated
> If a deployment is ACTIVE it can perform its normal operation
> If a deployment is UNINSTALLED it can be removed from the system
> The task here is mainly to rename/revisit the deployment phases

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