StrategyRegistrationProvider does not properly handle implementations from different classloader

Description

This is a follow-up of that broke a test for us on upgrade from 5.4.3 to 5.4.4.

The reason why the sub-type check fails is because those two classes are loaded by different classloaders. We've had a round of investigation as how to workaround the problem in our test and this comment provides valuable insight.

Environment

None

Status

Assignee

Yoann Rodière

Reporter

Stéphane Nicoll

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

backportDecision

None

Components

Affects versions

5.4.4

Priority

Major
Configure