2:54 p.m.
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
9:38 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on JBAS-9020:
----------------------------------------
Is the intent here that zipped archives are going to be served directly from the
deployments/ dir?
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
11:13 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
Brian Stansberry updated JBAS-9020:
-----------------------------------
Fix Version/s: 7.0.0.Beta4
(was: 7.0.0.CR1)
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.Beta4
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
10:47 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on JBAS-9020:
-------------------------------------
I believe the third section of xml should be:
{noformat}
<deployment name="foo.ear" runtime-name="foo.ear">
<fs-archive path="deployments/foo.ear"
relative-to="jboss.server.base.dir"/>
</deployment>
{noformat}
{noformat}
<deployment name="foo.ear" runtime-name="foo.ear">
<fs-exploded path="deployments/foo.ear"
relative-to="jboss.server.base.dir"/>
</deployment>
{noformat}
The assumption being that we're talking deployment content here which can come from
different places.
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.Beta4
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
5:53 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-9020:
-----------------------------------
Yes that is correct but only because it doesn't usually make sense to flatten an EAR
and a WAR together. It should however be possible to combine multiple content sources
into one deployment (they will each be a different resource root; this covers an ERD
requirement to support deployment content overlays).
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.Beta4
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
4:07 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on JBAS-9020:
-------------------------------------
So it becomes something like:
{noformat}
<deployment name="foo.ear" runtime-name="foo.ear">
<content id="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
<fs-archive root="myejb.jar" path="archives/someejb.jar"
relative-to="jboss.server.base.dir"/>
<fs-exploded root="myweb.war" path="archives/someweb.war"
relative-to="jboss.server.base.dir"/>
<content root="lib/additional-lib.jar"
id="123456789abcdef0000000000000000000000001"/>
</deployment>
{noformat}
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.Beta4
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
4:09 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
Carlo de Wolf edited comment on JBAS-9020 at 4/8/11 5:08 AM:
-------------------------------------------------------------
So it becomes something like:
{noformat}
<deployment name="foo.ear" runtime-name="foo.ear">
<content id="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
<fs-archive root="myejb.jar" path="archives/someejb.jar"
relative-to="jboss.server.base.dir"/>
<fs-exploded root="myweb.war" path="archives/someweb.war"
relative-to="jboss.server.base.dir"/>
<content root="lib/additional-lib.jar"
id="123456789abcdef0000000000000000000000001"/>
<url root="moreweb.war"
path="http://somehost/moreweb.jar"/>
</deployment>
{noformat}
I've used archives instead of deployments, because deployments has different
implications.
was (Author: wolfc):
So it becomes something like:
{noformat}
<deployment name="foo.ear" runtime-name="foo.ear">
<content id="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
<fs-archive root="myejb.jar" path="archives/someejb.jar"
relative-to="jboss.server.base.dir"/>
<fs-exploded root="myweb.war" path="archives/someweb.war"
relative-to="jboss.server.base.dir"/>
<content root="lib/additional-lib.jar"
id="123456789abcdef0000000000000000000000001"/>
</deployment>
{noformat}
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.Beta4
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
8:38 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-9020:
-----------------------------------
Yeah, using root="" like that is a good idea, I didn't think of it.
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.Beta4
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
11 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on JBAS-9020:
----------------------------------------
If the goal is to use this to support overlays, we need to consider some notion of
priorities or ordering.
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.Beta4
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
11:16 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-9020:
-----------------------------------
It should be fairly straightforward to just use the sequence ordering in configuration/add
operation. First listed, first resource root.
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.Beta4
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
12:43 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on JBAS-9020:
----------------------------------------
Yeah, it just needs to be considered when designing the model structure. E.g. if all the
content is stored in an attribute of a deployment resource, operation handlers can do what
they want. But if each piece of content is itself a resource (which seems more natural),
the "add" operation handling is going to append each one to the end of the
(Property)List of the deployment resource's children. No insertion in the middle.
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.Beta4
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
1:19 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-9020:
-----------------------------------
Yeah to change order it would have to be a "replace all" kind of thing. And,
incidentally, any content list change would have to trigger a redeploy if we want to keep
things consistent.
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.Beta4
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
11:53 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-9020) Deployment content management enhancement
[
https://issues.jboss.org/browse/JBAS-9020?page=com.atlassian.jira.plugin....
]
Carlo de Wolf reassigned JBAS-9020:
-----------------------------------
Assignee: Carlo de Wolf
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
Assignee: Carlo de Wolf
Fix For: 7.0.0.Beta4
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
6:06 a.m.
New subject: [JBoss JIRA] Commented: (AS7-431) Deployment content management enhancement
[
https://issues.jboss.org/browse/AS7-431?page=com.atlassian.jira.plugin.sy...
]
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
3:21 a.m.
New subject: [JBoss JIRA] Resolved: (AS7-431) Deployment content management enhancement
[
https://issues.jboss.org/browse/AS7-431?page=com.atlassian.jira.plugin.sy...
]
Carlo de Wolf resolved AS7-431.
-------------------------------
Resolution: Done
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
3:23 a.m.
New subject: [JBoss JIRA] Reopened: (AS7-431) Deployment content management enhancement
[
https://issues.jboss.org/browse/AS7-431?page=com.atlassian.jira.plugin.sy...
]
Carlo de Wolf reopened AS7-431:
-------------------------------
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
3:23 a.m.
New subject: [JBoss JIRA] Resolved: (AS7-431) Deployment content management enhancement
[
https://issues.jboss.org/browse/AS7-431?page=com.atlassian.jira.plugin.sy...
]
Carlo de Wolf resolved AS7-431.
-------------------------------
Resolution: Partially Completed
Deployment manager API has been rewritten to allow for multiple content items. The actual
processing of multiple contents is not yet implemented.
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
5509
days inactive
5607
days old
16 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Carlo de Wolf (JIRA)
-
David Lloyd (JIRA)