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

[GSS](7.2.z) [WFCORE-323] Validate composite operation steps just before executing them

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Not a Bug
    • Major
    • None
    • None
    • Management
    • Finally it was not needed to integrate the other changes needed in 7.2.8.

    Description

      Say we have a composite operation with 2 steps:

      1) /extension=org.jboss.as.messaging:add
      2) /subsystem=messaging:add

      This will fail:

      Failed to execute batch: JBAS014739: No handler for add at address
      [("subsystem" => "messaging")]

      This fails because at the time of validation the /subsystem=messaging:add is not valid.

      To illustrate, the execution order is

      Validate 1-2
      1
      2

      A possible solution is to convert this to the following:

      V1
      1
      V2 (works now because 1 has registered the subsystem API)
      2

      I think that should work but it's a very complex area, particularly in a managed domain, so it's not at all certain this would prove feasible.

      Attachments

        Issue Links

          clones

          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) WFCORE-323 Validate composite operation steps just before executing them

          • 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

          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-18665 (7.3.z) Validate composite operation steps just before executing them

          • 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 blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18657 (7.2.z) [HAL-1653] Topology is not refreshed automatically after restart the domain

          • 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.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18655 (7.2.z) [HAL-1663] Two error dialog messages when DC is starting and user executes lifecycle operations on slave servers

          • 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

          Activity

            People

              rhn-support-rmartinc Ricardo Martin Camarero
              rhn-support-rmartinc Ricardo Martin Camarero
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: