[jboss-jira] [JBoss JIRA] (WFCORE-973) JMX - Non string attributes dont work well with expressions & min/max

[Enrique González Martínez (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994288#comment-12994288 ] 

Enrique González Martínez edited comment on WFCORE-973 at 9/10/15 3:23 AM:
---------------------------------------------------------------------------

Attached the stack trace.
The SimpleTypeConverter calculates the opentype as String if the AD allows an expression. That makes the situation odd for simple types.  
The consistency of the attributes is checked during the creation of the openmbean. If these conversions from simple types (INT) to strings take place and there is a min-max constraint, then it could throw an exception.

Example: 
AD defined as INT (allows expressions) {defaultValue :5, minValue = 4, maxValue= 10}
 
Those numbers are converted to Strings. That means the creation fails: defaultValue > maxValue (String comparison "5" > "10"). 

I cannot see a solution without overwriting the openmbean behavior (standard java rt lib).



> JMX - Non string attributes dont work well with expressions & min/max
> ---------------------------------------------------------------------
>
>                 Key: WFCORE-973
>                 URL: https://issues.jboss.org/browse/WFCORE-973
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management, JMX
>            Reporter: Tomaz Cerar
>            Assignee: Enrique González Martínez
>            Priority: Minor
>         Attachments: stacktrace.log
>
>
> See ModelControllerMBeanTestCase.java:255
> problem is in conversion of attributes and when we have expressions jmx attribute type becomes String even if AD is of type INT
> And if attribute has min/max setting mbean fails validation upon creation
> I am not actually sure how we can fix this.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)