(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.
Big .war's, mainly on remote
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.