Move away from use of Enhydra developed DataSource for JTA testing

Description

It really does not interop well with JTA TransactionManager which is unfortunately the whole point. Longer term would still like to look at leveraging IronJacamar, but it unfortunately still has its issues in terms of non-easy use in cases like ours. So for now, lets just resurrect the custom DataSource notion.

Environment

None

Status

Assignee

Steve Ebersole

Reporter

Steve Ebersole

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Priority

Major
Configure