Bug 851186

Summary: Infinispan cache container creation Start parameter check/uncheck doesn't work correct
Product: [Other] RHQ Project Reporter: Armine Hovsepyan <ahovsepy>
Component: PluginsAssignee: Stefan Negrea <snegrea>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: low    
Version: JON 3.1.1CC: hrupp, mfoley, snegrea
Target Milestone: ---   
Target Release: RHQ 4.5.0   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 855982 (view as bug list) Environment:
Last Closed: 2013-09-01 06:15:00 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 707223, 855982    

Description Armine Hovsepyan 2012-08-23 08:48:27 EDT
Description of problem:
Infinispan cache container creation Start parameter check/uncheck doesn't work correct
During the creation of new cache container under infinispan resource if you uncheck Start property, LAZY load check box is pre-selected, while saving the container will save Start config as unchecked. 

Version-Release number of selected component (if applicable):
JON 3.1.1 ER3
EAP 6.0

How reproducible:

Steps to Reproduce:
1. click on infinispan resource under EAP
2. click on Crete child resource - cache container 
3. put any name and click continue
4. uncheck Start config param - LAZY is pre-selected
5. Click on Finish button

Steps to Reproduce:
1. Repeate 1-4 steps from previous scenario
2. Click on LAZY check box once more (even if it's preselected)
3. Click on Finish button

Actual results:
New cache container is created with unchecked Start config parameter

Expected results:
New cache container is created with LAZY Start config parameter

Additional info:
If during the creation you click "EAGER" check box and click finish or click "EAGER" and then LAZY and then finish - correct Start parameter will be saved.

nothing big - but makes inconvenience
Comment 1 Stefan Negrea 2012-09-10 16:20:00 EDT
This is not a plugin problem, it is purely a GUI problem. The logic for default values and set/unset checkbox is counter-intuitive. 

The way default values are applied to properties was updated to give a natural user experience. Behaviour after the update:
1) If the field is unset then disable field and set value to null
2) If the field is set then enable field and load saved value
3) On unset change from true to false, enable field and load default value if not null
4) On unset change from false to true, disable field and set value to null
Comment 3 Heiko W. Rupp 2013-09-01 06:15:00 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.