Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Partially Completed
    • Affects Version/s: None
    • Fix Version/s: 7.0.0.CR1
    • Component/s: None
    • Labels:
      None
    • Estimated Difficulty:
      Medium

      Description

      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:

          <deployment name="foo.ear" runtime-name="foo.ear" sha1="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
      

      It should be structured as:

          <deployment name="foo.ear" runtime-name="foo.ear">
              <content id="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
          </deployment>
      

      If there is filesystem content it should be listed differently:

          <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>
      

      For filesystem hot-deployment purposes, it is up to the FS scanner to take care of tracking and removing deployments whose content was removed.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  wolfc Carlo de Wolf
                  Reporter:
                  dmlloyd David Lloyd
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  11 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: