[jboss-as7-dev] Allign deployment phases with OSGi terminology

[David M. Lloyd]

On 07/26/2012 09:04 AM, Thomas Diesler wrote:
> Folks,
>
> this is related to AS7-3585 <https://issues.jboss.org/browse/AS7-3585>
>
> I propose the following mapping
>
> 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
>
> In a first commit I would simple rename the phases and associated
> constants but not the DUPs that have the phase in their class name.
> This would also address the need for a new phase (POST_ACTIVATE) that is
> needed for OSGi webapp integration.
>
> Thoughts?

Not for 7.x.  And I'm not 100% sure 8.x will work 100% the same way. 
Even if it did I don't think there's a great benefit to aligning to the 
OSGi way - it makes the other 90% make a lot less sense.  Phases are 
named in terms of what is available when the phase is complete.  As it 
is, we should not have added a new phase; I still see that as a mistake. 
  You can achieve the same effect by interposing services during the 
regular deployment lifecycle.

Instead OSGi should probably have a parallel service chain that uses 
dependencies on the primary chain in order to sync up with normal 
deployments.

-- 
- DML