[
https://issues.jboss.org/browse/AS7-2777?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on AS7-2777:
-----------------------------------
I think the mapping for what we have today should be:
deploy = add
start = deploy
stop = undeploy
undeploy = remove.
As to the OSGi case, we have that long standing deployment chain refactor (pushed outside
of 7.1) that would better handle the INSTALLED/RESOLVED case. That scenario would involve
having the OSGi deployment chains stop mid way through and lazily start based on an
external demand (osgi decides to move to installed). We could, at that time decide to map
start in 88 to mean force a full start (assuming that's helpful)
Add notion of start/stop for deployments
----------------------------------------
Key: AS7-2777
URL:
https://issues.jboss.org/browse/AS7-2777
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management, JSR-88, OSGi, Server
Reporter: Thomas Diesler
Assignee: Thomas Diesler
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