Misspell on Transaction Isolation should throw an error in DataSource Configuration

If you by a mistake set a transaction isollation misspelled, for instance (READ_COMMITTED instead of TRANSACTION_READ_COMMITTED) the datasource is accepted with its default transaction isolation what could cause inexpected behaviors.

I know it looks a simple issue, but i guess a simple change would make it easier to find confiburation problems.