Red Hat Bugzilla – Bug 535056
inputs for unset optional props are no longer disabled as they should be after an open map member prop is deleted via DELETE button
Last modified: 2013-08-05 20:33:01 EDT
I spent several hours troubleshooting this and wasn't able to get it to work. I think it should be tabled until post-x.2. The workaround is to uncheck and then recheck the Unset checkboxes for any optional integer props before clicking SAVE to update the config. Otherwise, you will see validation errors for those props saying "" is not a valid value for integer property 'foobar'.
ian, what are the things we modeled as open map props today across all plugins? i'm trying to get a sense for how often end users will see this. if this is open map type is used for any common and/or important config props, i would want to get a proper fix into x.2 release.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1792
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.
new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
Closing per 19-Aug triage -- this bug will be made obsolete per UI redesign.