Bug 752431 - [jboss-as-5] type-mapping value for datasources is not validated against the set of configure type mappings
[jboss-as-5] type-mapping value for datasources is not validated against the ...
Status: NEW
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
Unspecified Unspecified
medium Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2011-11-09 08:37 EST by Stefan Negrea
Modified: 2011-11-09 10:37 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stefan Negrea 2011-11-09 08:37:24 EST
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):

How reproducible:

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.
Comment 1 Stefan Negrea 2011-11-09 08:38:20 EST
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.

Note You need to log in before you can comment on or make changes to this bug.