Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-1983

Root cause of failing parsing should be used as failure description

    Details

      Description

      It happens that the CLI does a custom parsing of the value in case ModelNode.fromString fails (whatever the exception).
      The issue is that the custom parsing doesn't follow the ModelNode parsing syntax and parse everything as String. So the resulting ModelNode that is serialised and sent to the server has been transformed.

      I am surprised that we don't have more of such failures. For example, when numbers are located inside custom complex structure such as:

      {mynumber=9999}

      that will be sent as an OBJECT containing a STRING although the valid DMR syntax

      {"my number"=>999}

      would be sent as an OBJECT containing an INT.

      Some server side subsystems are smart enough to call into asXXX methods and not check the type?

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ehugonnet Emmanuel Hugonnet
                  Reporter:
                  jdenise Jean Francois Denise
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: