[
https://issues.jboss.org/browse/AS7-2777?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler edited comment on AS7-2777 at 11/28/11 3:02 AM:
---------------------------------------------------------------
It is of course a matter of defining the various states and the lifecycle steps between
them. Here is what I had in mind
* 'deploy' transitions to state INSTALLED - the metadata is valid
* a deployment that is INSTALLED can be RESOLVED (i.e. a classloader can get attached).
This happens at the discretion of the runtime
* 'start' transitions from INSTALLED to RESOLVED (if not happened already) and
further to ACTIVE. The deployment's activator is called - the respective services get
activated
* 'stop' transitions from ACTIVE to RESOLVED. The respective services get
deactivated
* 'undedploy' transitions to UNINSTALLED - is not available for new wirings. Ready
for removal by the runtime
You can repeatedly start/stop a deployment without revaluating its metadata, do the
unpacking, etc. With the current implementation I believe this is not the case - no DUPs
are called for operation 'add' if I'm not mistaken.
was (Author: thomas.diesler):
It is of course a matter of defining the various states and the lifecycle steps
between them. Here is what I had in mind
* 'deploy' transitions to state INSTALLED - the metadata is valid
* a deployment that is INSTALLED can be RESOLVED (i.e. a classloader can get attached).
This happens at the discretion of the runtime
* 'start' transitions from INSTALLED to RESOLVED (if not happened already) and
further to ACTIVE. The deployment's activator is called - the respective services get
activated
* 'stop' transitions from ACTIVE to RESOLVED. The respective services get
deactivated
* 'undedploy' transitions to UNINSTALLED - is not available for new wirings. Ready
for removal by the runtime
Add notion of start/stop for deployments
----------------------------------------
Key: AS7-2777
URL:
https://issues.jboss.org/browse/AS7-2777
Project: Application Server 7
Issue Type: Task
Components: Domain Management, JSR-88, OSGi
Reporter: Thomas Diesler
Assignee: Brian Stansberry
Fix For: 7.1.0.Final
The JSR88 deployemt API allows control over the full deployment lifecycle
* deploy
* start
* stop
* undeploy
OSGi deployments (i.e. bundles) also have the notion of start/stop
This should be reflected in the management API for deployments.
--
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