Description of problem: There is an empty value in the dropdown box of Transaction Isolation field of a datasource. However, it already has TRANSACTION_NONE option. Version-Release number of selected component (if applicable): JBoss EAP 6.2.2 How reproducible: 1) Create a datasource in JBoss EAP 6.2.2 2) Select the datasource, disable it. 3) Go to "Connection" tab and click the Edit button. 4) For the field "Transaction isolation", select "TRANSACTION_READ_COMMITTED". Now again select the empty value. Click the save button. Now the dropdown box becomes red and says missing selection message. Actual results: management console shows a error saying that is a missing selection Expected results: no blanck option as the dropbox alredy has the TRANSACTION_NONE option.
The empty value in the drop down box means "undefined". According to the management model the transaction attribute is defined as "transaction-isolation" => { "type" => STRING, "description" => "Set the java.sql.Connection transaction isolation level. Valid values are: TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE and TRANSACTION_NONE", "expressions-allowed" => true, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } Given that definition the transaction attribute can be undefined. IMHO there should be a default value specified in the model though. The error message which is raised when there was a value and you want to change back to an empty value is a bug.
Harald Pehl <hpehl> updated the status of jira HAL-393 to Coding In Progress
Harald Pehl <hpehl> updated the status of jira HAL-393 to Resolved
Fixed by HAL 2.4.0.Final BZ1144083. Setting to MODIFIED. No plans yet to include this in EAP 6.3 CP.
Verified for HAL 2.4.8.Final-redhat-1 in EAP 6.4.0.DR11