-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
Many resources contain flags in form of boolean attributes. Common examples are
"enabled" => { "type" => BOOLEAN, "expressions-allowed" => true, }
or
"statistics-enabled" => { "type" => BOOLEAN, "expressions-allowed" => true, }
If the value of these attributes is an expressions, the attribute cannot be easily evaluated as either true of false. This is an issue when the UI state depends on a concrete boolean value.
For example, the available actions in the datasource column depend on the enabled state of the datasource. If enabled is an expression it is unknown when the datasource is read from the management model. In this case the enabled state is set to false which might not reflect the real state (in case the expression evaluates to true).
Find a way to have a defined UI state even if the boolean attributes contain expressions.
- is incorporated by
-
JBEAP-16534 [GSS](7.2.z) HAL-1572 - Console fails to display datasources correctly when a datasource has a property substitution
- Closed
- is related to
-
JBEAP-23617 (7.4.z) HAL-1793 - Console shows "Statistics Disabled" but "wildfly.statistics-enabled" is set
- Closed
-
WFLY-14889 Enable datasource statistics is not handled properly in management console
- Open