I started using this library (or technically mimicking what it does as I couldn't find a way to extend it) and I stumbled across an issue with Spring referencing beans created in this way when referenced as a qualifier.
I submitted the issue to Spring with a test - you cna find it at https://jira.spring.io/browse/SPR-11915. They've just fixed it and they've going to backport it into the 3.2 and maybe 4.0 branches so you might want to take in their updates.
You'll see this issue as soon as you register a transaction manager with a custom name and try to use @Transactional("name") somewhere else. I have a custom piece of YAML config where you have multiple databases, hence the need to at runtime configure multiple transaction managers.
I started using this library (or technically mimicking what it does as I couldn't find a way to extend it) and I stumbled across an issue with Spring referencing beans created in this way when referenced as a qualifier.
I submitted the issue to Spring with a test - you cna find it at https://jira.spring.io/browse/SPR-11915. They've just fixed it and they've going to backport it into the 3.2 and maybe 4.0 branches so you might want to take in their updates.
You'll see this issue as soon as you register a transaction manager with a custom name and try to use @Transactional("name") somewhere else. I have a custom piece of YAML config where you have multiple databases, hence the need to at runtime configure multiple transaction managers.