[jboss-jira] [JBoss JIRA] (WFCORE-2645) JMX interface should allow non-string values in the jboss.as.expr JMX domain

[ https://issues.jboss.org/browse/WFCORE-2645?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2645: ------------------------------------- Description: Perhaps an enhancement, perhaps a bug. TypeConverters.SimpleTypeConverter.toModelNode() is casting the value to String in the expression case (i.e. for jboss.as.expr). This means if the client sends a non-string, i.e. something in the type that would be normal in the jboss.as domain, e.g. Boolean, the call will fail with a class cast exception. It seems like it would be easy enough to handle non-String. That would allow client code written for jboss.as to more easily deal with jboss.as.expr as well. Our testsuite's JmxManagementInterface client being the specific example that led me to file this. (My work on WFCORE-2633 was impacted when I wanted to use JmxManagementInterface to write a boolean value.) was: Perhaps an enhancement, perhaps a bug. TypeConverters.SimpleTypeConverter.toModelNode() is casting the value to String in the expression case (i.e. for jboss.as.expr). This means if the client sends a non-string, i.e. something in the type that would be normal in the jboss.as domain, e.g. Boolean, the call will fail with a class cast exception. It seems like it would be easy enough to handle non-String. That would allow client code written for jboss.as to more easily deal with jboss.as.expr as well. Our testsuite's JmxManagementInterface client being the specific example that led me to file this. (My work on WFCORE-2633 was impacted.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)