Re: [jboss-as7-dev] Allign deployment phases with OSGi terminology
The problem is also with Phase.REGISTER, which is an awkward name
because Phase.INSTALL (which captures the meaning) was already taken
Phase.*MODULE* is awkward because a Module may not be present - this is
increasingly so because we support a wider range of OSGi bundle
deployments (e.g. jdbc drivers and other 3rd party artefacts get
distributed as bundles)
Phase.INSTALL is awkward (as you say) because according to the OSGi
standard it means "install", but don't resolve/activate. In AS7 it means
"activate"
-thomas
On 07/26/2012 10:55 PM, Ondřej Žižka wrote:
> is that Phase.INSTALL is confusing with the OSGi meaning of INSTALL. I
> always have to use many words when I talk about 'install' in AS7. Now
> that we support war,ejb3,cdi deployments as OSGi bundles this is even
> more so.
>
How about just renaming INSTALL -> ACTIVATE, would that work?
I just started learning the AS lifecycles, so I don't really know, but
the current naming seemed logical to me, and OSGi would not help me to
understand the process much if it was in place...
my2c
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Attachments:
- attachment.html (text/html — 1.9 KB)