]
Brian Stansberry commented on WFCORE-429:
-----------------------------------------
Agreed that we need to sort out the requirements.
I think the relevant concepts need to be clarified. There are two aspects of deployments:
1) Exploded vs zipped
2) Content used by the server is stored in the content repo and manipulated via the
management API (aka Managed) vs stored externally and manipulated via the filesystem (aka
unmanaged).
We support 3 of the 4 possible combinations thereof. We don't support Exploded +
Managed.
The scanner is just a tangent; it's an automated client that utilizes two of the four
permutations: Exploded + unmanaged and zipped + managed. It doesn't use zipped +
unmanaged because it doesn't need to.
Based on the first few comments on EAP7-204, my expectation was the first goal was to add
the 4th of the four combinations: Exploded + managed. Doing so removes any requirement for
the client to have access to the server/host filesystem.
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.