Improvement - Optional webdeployment, WarManager and Waiting-State
------------------------------------------------------------------
Key: PAXWEB-240
URL: http://issues.ops4j.org/browse/PAXWEB-240
Project: Pax Web
Issue Type: Improvement
Affects Versions: 1.0.0
Reporter: Achim Nierbeck
Assignee: Alin Dreghiciu
Fix For: 1.0.1
Provided by, Hiriam
(1): If the bundle header 'Webapp-Deploy' is to false, then the war is
not published when it's first found.
(2): added a simple org.ops4j.pax.web.extender.war.WarManager
interface which can be used start/stop published wars.
(3): added a new WAITING state to the WebEvent class to represent the
case where a 2nd war deployment is done on a context that has already
been deployed.
My fork is at:
https://github.com/chirino/org.ops4j.pax.web
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
