When connection validation method is set to custom-validation, admin console calls the Connector Runtime API getValidationClassNames to get a list of custom validation class names available for the particular database vendor. This API needs to change to take in a datasource classname or a driver classname.
As of now, this does not work because the advanced tab in GUI has settings to turn on the connection validation to one of the types. After a pool is created, when the user navigates to the advanced tab, the value of the database vendor is lost and as a result, the getValidationClassNames API cannot be invoked.
This needs to be fixed for displaying the validation class names in GUI.