Class IsolationLevelDataSourceRouter

java.lang.Object
org.springframework.jdbc.datasource.AbstractDataSource
org.springframework.jdbc.datasource.lookup.AbstractRoutingDataSource
org.springframework.jdbc.datasource.lookup.IsolationLevelDataSourceRouter
All Implemented Interfaces:
Wrapper, CommonDataSource, DataSource, InitializingBean
public class IsolationLevelDataSourceRouter extends AbstractRoutingDataSource
DataSource that routes to one of various target DataSources based on the current transaction isolation level. The target DataSources need to be configured with the isolation level name as key, as defined on the TransactionDefinition interface.

This is particularly useful in combination with JTA transaction management (typically through Spring's JtaTransactionManager). Standard JTA does not support transaction-specific isolation levels. Some JTA providers support isolation levels as a vendor-specific extension (for example, WebLogic), which is the preferred way of addressing this. As an alternative (for example, on WebSphere), the target database can be represented through multiple JNDI DataSources, each configured with a different isolation level (for the entire DataSource). IsolationLevelDataSourceRouter allows to transparently switch to the appropriate DataSource based on the current transaction's isolation level.

For example, the configuration can look like the following, assuming that the target DataSources are defined as individual Spring beans with names "myRepeatableReadDataSource", "mySerializableDataSource", and "myDefaultDataSource": 

<bean id="dataSourceRouter" class="org.springframework.jdbc.datasource.lookup.IsolationLevelDataSourceRouter">
  <property name="targetDataSources">
    <map>
      <entry key="ISOLATION_REPEATABLE_READ" value-ref="myRepeatableReadDataSource"/>
      <entry key="ISOLATION_SERIALIZABLE" value-ref="mySerializableDataSource"/>
    </map>
  </property>
  <property name="defaultTargetDataSource" ref="myDefaultDataSource"/>
</bean>
Alternatively, the keyed values can also be data source names, to be resolved through a DataSourceLookup: by default, JNDI names for a standard JNDI lookup. This allows for a single concise definition without the need for separate DataSource bean definitions. 
<bean id="dataSourceRouter" class="org.springframework.jdbc.datasource.lookup.IsolationLevelDataSourceRouter">
  <property name="targetDataSources">
    <map>
      <entry key="ISOLATION_REPEATABLE_READ" value="java:comp/env/jdbc/myrrds"/>
      <entry key="ISOLATION_SERIALIZABLE" value="java:comp/env/jdbc/myserds"/>
    </map>
  </property>
  <property name="defaultTargetDataSource" value="java:comp/env/jdbc/mydefds"/>
</bean>
Note: If you are using this router in combination with Spring's JtaTransactionManager, don't forget to switch the "allowCustomIsolationLevels" flag to "true". (By default, JtaTransactionManager will only accept a default isolation level because of the lack of isolation level support in standard JTA itself.) 
<bean id="transactionManager" class="org.springframework.transaction.jta.JtaTransactionManager">
  <property name="allowCustomIsolationLevels" value="true"/>
</bean>
Since:
2.0.1
Author:
Juergen Hoeller, Sam Brannen
See Also: