Consider leveraging [~yrodiere]'s work on support for named beans in ManagedBeanRegistry in supporting the work of StrategySelector.
This would seamlessly allow hosting different types of contracts in the underlying DI-container. E.g. looking up a specifically named {{ConnectionProvider}}, {{JtaPlatform}}, etc
For example, we could locate a Datasource by name from CDI/Spring container, or a named ConnectionProvider or a named JtaPlatform, etc. This is basically an extension of "short naming" expanding the places we can look to resolve the names |
|
