Description of problem: lifespan field (infinispan -> local cache -> expiration tab), the doc says it is a long field, but web console doesn't let me put a value higher than Integer (see web_console2.png). JBoss CLI is fine. This is bad because, we want to fix the lifespan to 30 days, and it is not possible. Version-Release number of selected component (if applicable): EAP 6.3.X also WildFly HAL upstream. How reproducible: Just try to set a Long number in the lifespan expiration field Steps to Reproduce: 1. Start the EAP 2. Go to Web-Console > infinispan > local cache > expiration tab 3. Try to set a high number. Actual results: Is printed the message: "Invalid numeric value". Expected results: Long Values should be accepted. Additional info: Workaround: Configure the lifespan expiration Through CLI or xml file. =================== I was going through source code and I found this: This LocalCache (used as example for the tests) class have the correct declaration : https://github.com/hal/core/blob/9a5f0edbaca71b54aea2df56dc659b420d6f752c/gui/src/main/java/org/jboss/as/console/client/shared/subsys/infinispan/model/LocalCache.java#L268 This class have a switch case where the case LONG calls the NumberBoxItem: https://github.com/hal/core/blob/8949ed6dc259feb366d17ec2078c7799f32d7763/gui/src/main/java/org/jboss/as/console/mbui/widgets/ModelNodeFormBuilder.java#L244 The NumberBoxItem have the max value to Integer: private int max = Integer.MAX_VALUE; and then all parses are to Integer: https://github.com/hal/ballroom/blob/master/widgets/src/main/java/org/jboss/ballroom/client/widgets/forms/NumberBoxItem.java#L113 https://github.com/hal/ballroom/blob/master/widgets/src/main/java/org/jboss/ballroom/client/widgets/forms/NumberBoxItem.java#L167 I have some tests by made some changes in the NumberBox.java. I am attached the modified class for your review and the print screen with the result. Thanks.
Harald Pehl <hpehl> updated the status of jira HAL-638 to Coding In Progress
Harald Pehl <hpehl> updated the status of jira HAL-638 to Resolved
Fixed in Ballroom 2.3.1
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Fixed in ballroom 2.1.12.Final https://github.com/hal/ballroom/commit/831442fb7db48c999c1cfbcc82ec9c54c0206188
Verified with EAP 6.4.12.CP.CR1
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.