Description of problem: RHQ fails to validate the value of type mapping for datasource configurations. The user can enter an arbitrary type mapping that is not defined in conf/standardjbosscmp-jdbc.xml. This does affect the configuration of the particular datasource making it unusable, but it does not affect anything else. The server will display errors on start but will continue to work as expected. Version-Release number of selected component (if applicable): 4.2.0 How reproducible: Always Steps to Reproduce: 1. Add an AS5 instance to RHQ inventory 2. Navigate to the datasource resource's Configuration tab 3. Type an invalid type mapping name (eg. "Test123") under Advanced / Metadata / Type Mapping Actual results: There are NO errors on saving the configuration update. Expected results: The type mapping should be validated, flagged as bad value, and errors should be displayed. Additional info: This validation process needs to be implemented for all available types datasources.
The proposed validation is complex because it involves retrieving current type mappings from the JMX interface; the list of type mappings is not available on the profile service.