[jboss-jira] [JBoss JIRA] (WFCORE-1983) Root cause of failing parsing should be used as failure description

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-1983:
-------------------------------------
    Component/s: Domain Management
                     (was: Server)


[~jdenise] Thanks for digging into this!

Please use "Domain Management" as the component for any server side management issues, unless the are subsystem-specific and there is a component for the subsystem, in which case you use that.


> Root cause of failing parsing should be used as failure description
> -------------------------------------------------------------------
>
>                 Key: WFCORE-1983
>                 URL: https://issues.jboss.org/browse/WFCORE-1983
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Jean-Francois Denise
>            Assignee: Brian Stansberry
>
> 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?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)