[jboss-jira] [JBoss JIRA] Created: (JBAS-9020) Deployment content management enhancement
Deployment content management enhancement
-----------------------------------------
Key: JBAS-9020
URL: https://issues.jboss.org/browse/JBAS-9020
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Fix For: 7.0.0.CR1
In order to keep deployment state sane and meet various external requirements, we need to
support multiple content items per deployment.
Presently deployments are permanently, uniquely identified by SHA1. We need to move this
SHA1 identifier to the content of the deployment element. So rather than:
{noformat}
<deployment name="foo.ear" runtime-name="foo.ear"
sha1="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
{noformat}
It should be structured as:
{noformat}
<deployment name="foo.ear" runtime-name="foo.ear">
<content id="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
</deployment>
{noformat}
If there is filesystem content it should be listed differently:
{noformat}
<deployment name="foo.ear" runtime-name="foo.ear">
<fs-archive path="deployments/foo.ear"
relative-to="jboss.server.base.dir"/>
<fs-exploded path="deployments/foo.war"
relative-to="jboss.server.base.dir"/>
</deployment>
{noformat}
For filesystem hot-deployment purposes, it is up to the FS scanner to take care of
tracking and removing deployments whose content was removed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira