Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5808

(7.0.z) When replacing deployment the name attribute should be selected from selected deployment and not from the uploaded filename

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.4.CR1, 7.0.4.GA
    • 7.0.2.CR1
    • Web Console
    • None
    • EAP 7.0.4

    Description

      User wants to replace deployed test.war with new version test-2.war.
      Using CLI it's possible by running command 

      :full-replace-deployment(name=test.war, content=[{url=file:///path/to/test-2.war}])

      but when user selects test.war deployment in console and wants to replace it with test-2.war he gets failure since HAL uses uploaded filename as the value of name attribute of the full-replace-deployment operation.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5795 (7.1.0) When replacing deployment the name attribute should be selected from selected deployment and not from the uploaded filename

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7467 (7.1.0) When replacing deployment the name attribute should be selected from selected deployment and not from the uploaded filename

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. HAL-1173 When replacing deployment the name attribute should be selected from selected deployment and not from the uploaded filename

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-5731 (7.0.z) Upgrade HAL from 2.8.27.Final to 2.8.28.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              pjelinek@redhat.com Pavel Jelinek
              Pavel Jelinek Pavel Jelinek
              Pavel Jelinek Pavel Jelinek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: