]
Brian Stansberry commented on WFCORE-429:
-----------------------------------------
[~luck3y] FYI. This relates to the managed exploded deployment EAP7-204 JIRA, although
reading this it implies it may work for non-exploded deployments too, which I don't
think we should support, except via the deployment-overlay feature.
At this point this JIRA should be regarded as informational, an input to the requirements
gathering around EAP7-204. Perhaps it becomes the upstream JIRA for EAP7-204, perhaps it
becomes extra stuff to do later, perhaps it gets closed and other JIRAs get opened.
Incremental redeployment (single file update) over management API
-----------------------------------------------------------------
Key: WFCORE-429
URL:
https://issues.jboss.org/browse/WFCORE-429
Project: WildFly Core
Issue Type: Feature Request
Components: CLI, Domain Management
Reporter: Ondrej Zizka
Labels: deploy, deployment, incremental, redeployment
(Based on JBDS use case - see EAP6-1)
See also
https://mojo.redhat.com/docs/DOC-934058 for notes
By incremental redeployment, we mean the situation when something is deployed, and after
changes (in IDE e.g.), only that single file (.jsp, .xml, .class) would be re-deployed to
the server, *over management API* - which is, you'd give it a stream and a path where
it belongs in the deployment, and the operation would accept that file and put it to the
right place in VFS, clear caches etc.
Use cases:
Big .war's, mainly on remote
Cloud deployments
Also, you loose sessions etc.
"JSP recompile on file update" - mgmt API operation - added in WildFly 8?
Not expected to work in domain mode.
Stuart said that session persistence is implemented in WFly 8, but not the incremental
redeployment.