Details

      Description

      In certain cases it is useful to send back, to client, some sort of context information about the outcome of operation. For instance, when change in configuration warrants another one and without it, after reload/restart server could not operate properly. For instance JBEAP-7284.

      Scope of this enhancement are:
      a) way to send back information
      b) control level of "information" - just like in case of loggers

      a) Information will be sent in response headers, under "warnings" key. Each entry, "warning" will contain operation, address, level/severity and i18n string with proper ID.
      b) default level threshold would be "WARNING", if user requires more detailed information, he can request it via operation-headers->warninig-level

      Example:

      {
          "outcome" => "success",
          "response-headers" => {
              "warnings" => [
                  {
                      "warning" => "WFLYCTL0436: Couldn't convert 'XXX' into proper warning level, threshold falling back to 'ALL'. Possible values: SEVERE,WARNING,INFO,CONFIG,FINE,FINER,FINEST",
                      "level" => "ALL",
                      "operation" => {
                          "address" => [
                              ("subsystem" => "undertow"),
                              ("server" => "default-server"),
                              ("http-listener" => "default")
                          ],
                          "operation" => "write-attribute"
                      }
                  },
                  {
                      "warning" => "WFLYUT0090: Worker used in http-listener: 'puppet-master', must be used in remoting subsystem.",
                      "level" => "WARNING",
                      "operation" => {
                          "address" => [
                              ("subsystem" => "undertow"),
                              ("server" => "default-server"),
                              ("http-listener" => "default")
                          ],
                          "operation" => "write-attribute"
                      }
                  }
              ],
              "operation-requires-reload" => true,
              "process-state" => "reload-required"
          }
      }
      
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  baranowb Bartosz Baranowski
                  Reporter:
                  rhatlapa Radim Hatlapatka
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 4 days
                    4d