Caching SchemaResolver delegate with multiple data sources

Description

With multiple data sources, when the first data source to be loaded has a Java 1.7-compatible driver, the SchemaNameResolverJava17Delegate is chosen and cached. If another data source has a driver is not Java 1.7-compatible, the cached resolver is still used, and fails with an AbstractMethodError.

There is a workaround to set hibernate.schema_name_resolver to SchemaNameResolverFallbackDelegate.

Environment

None

Status

Assignee

Andrea Boriero

Reporter

Todd Gibson

Fix versions

Labels

None

backPortable

Backport?

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Worked in

5.1.12

Components

Affects versions

5.2.14
5.2.15

Priority

Minor
Configure