[jboss-jira] [JBoss JIRA] Commented: (AS7-431) Deployment content management enhancement
Carlo de Wolf (JIRA)
jira-events at lists.jboss.org
Thu May 12 07:06:32 EDT 2011
[ https://issues.jboss.org/browse/AS7-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601611#comment-12601611 ]
Carlo de Wolf commented on AS7-431:
-----------------------------------
https://github.com/jbossas/jboss-as/compare/e58e55d...442f752 has been merged.
> Deployment content management enhancement
> -----------------------------------------
>
> Key: AS7-431
> URL: https://issues.jboss.org/browse/AS7-431
> Project: Application Server 7
> Issue Type: Task
> Reporter: David Lloyd
> Assignee: Carlo de Wolf
> 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
More information about the jboss-jira
mailing list