[ https://issues.jboss.org/browse/WFCORE-1983?page=com.atlassian.jira.plugi... ] Jean-Francois Denise edited comment on WFCORE-1983 at 11/16/16 8:30 AM: ------------------------------------------------------------------------ I have looked at the server side handling of arguments for the read-resource (ReadResourceHandler). When the numbers or String are in range, aproper adaptation is made on the server side. :read-resource(recursive-depth="9"), :read-resource(recursive-depth=9L), :read-resource(recursive-depth=9.4), are property converted from STRING/LONG/DOUBLE to INT. With an out of range value (:read-resource(recursive-depth=999999999999)). The cli converts the out of range depth to STRING and send the request. The conversion to INT fails and the exception is swallowed in ModelTypeValidator.matches. The server side should keep a reference to the last thrown exception and throw that instead of the generic type mismatch. was (Author: jdenise): I have looked at the server side handling of arguments for the read-resource (ReadResourceHandler). The faulty operation is: :read-resource(recursive-depth=999999999999). The cli converts the out of range depth to STRING and send the request. The server handler validates each parameter and checks for the value type. The only valid type for recursive-depth is INT. So the operation fails with "WFLYCTL0097: Wrong type for 'recursive-depth'. Expected [INT] but was STRING". Same occurs for list-add.index. -- This message was sent by Atlassian JIRA (v7.2.3#72005)