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

Unclear exception when trying to do full-replace-deployment operation with wrong name attribute value

    XMLWordPrintable

Details

    • Hide
      1. deploy test.war
      2. :full-replace-deployment(name= test-2.war, content=[ {url=file:///path/to/test-2.war}

        ])

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

    Description

      in standalone mode user gets 

      "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"

      whereas in domain mode better but still confusing 

      "failure-description" => {"domain-failure-description" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"test-2.war\")]' not found"}

      I would rather expect something like "Original file to be replaced named test-2.war not found."
      Definitely not the NPE in standalone mode.

      Attachments

        Issue Links

          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-5897 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha8

          • 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.
          • Verified
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-6203 Improve error message upon attempting of full-replace of non-existing deployment

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1569 NPE when executing a full-replace-deployment operation followed by an add operation for the same deployment

          • 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

          Activity

            People

              chaowan@redhat.com Chao Wang
              pjelinek@redhat.com Pavel Jelinek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: