AbstractRoutingDataSource :- Importance of Thread Bound Transaction Context for lookup key
I am implementing AbstractRoutingDataSource in our project. From what i read AbstractRoutingDataSource is an abstract data source implementation that routes getConnection() calls to one of various target DataSources based on a lookup key. The latter is usually (but not necessarily) determined through some thread-bound transaction context. What I am wondering is ,what is the advantage of using a thread bound transaction context to determine the lookup key? When is it ideal to use such a method. Any help would be highly appreciated. Thanks in advance :)
Briefly, Bound Threads can change the attributes of the underlying lightweight process. and Lightweight processes are not cached when the bound threads exit. In Scheduling Context; Bound threads for System Scope and Unbound threads are Process Scope. [Docs Oracle, 2010] System Scope: compete for CPU with other system threads (such as Kernel Threads). Process Scope: compete for the CPU within the current process.
Spring MVC application don't work with Tomcat and Eclipse
How to draw a RGB Color Wheel in Java
Display alternate toString() Method with custom cell editor
Error when trying to test a mathematical proof
Wildfly 10 BouncyCastleCrypto ECDSA key spec not recognized
How to add multiple lines of text to a text area using javafx?
Make #ExceptionHandler handle every exception except AccessDeniedException?
How to sort list with multiple condition?
Exception on running IE web Driver
Spring dont see angular
Android resources error
How do I color tiles based on this?
ASTM 1381-02 Serial Interfacing with Medical Lab equipment
The UI can't control the Philips Hue Color lightbulb
How can i combine more than one getString into a textfield
EJB as WebService in Enterprise Application Project