[
https://issues.jboss.org/browse/AS7-2943?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-2943:
-------------------------------------
Assignee: Kabir Khan (was: Brian Stansberry)
Potentially this could be configurable via the host.xml <server> element; i.e.
people who want to avoid multiple copies could choose to use a shared repo. That
introduces the issue of how to GC the deployment repo though.
Make managed servers (domain mode) store deployments in their own
content repository
-------------------------------------------------------------------------------------
Key: AS7-2943
URL:
https://issues.jboss.org/browse/AS7-2943
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Kabir Khan
Priority: Blocker
Fix For: 7.1.0.Final
AS7-341 implements the removal of the deployed content in the domain
DeploymentRemoveHandler. However, since the managed servers use their HC's content
repository, if one of the servers failed removing the deployment from their model, the
content is wrongly removed from the HC repository since the error is not reported back.
Having each server maintain their own repo avoids this problem
--
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