HP Integrity NonStop J-Series - Manual (Page 69)

In this case, the definition ensures that the transactional advice defined by the
txAdvice
bean actually executes at the appropriate points in the program. Define a pointcut that
matches the execution of any operation defined in the MyService interface
(myServiceOperation). Associate the pointcut with the txAdvice using an advisor. The result
indicates that at the execution of a myServiceOperation, the advice defined by txAdvice
will be run.
Defining the Transaction Datasource
This section describes the steps to define the datasource that will be used by the transaction. For
more information on datasource configuration, see
“Configuring JDBC Driver for SQL/MX Database”
(page 63) .
Add the following lines in the applicationContext.xml file to create the datasource:
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
${jdbc.driver}
${jdbc.url}
${jdbc.user}
${jdbc.password}
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
classpath:jdbc.properties
NOTE: Here org.apache.commons.dbcp.BasicDataSource is used as the datasource.
Defining the PlatformTransactionManager
The PlatformTransactionManager is an interface; it is not tied to a lookup strategy such as
JNDI, thereby making it abstract while working with JTA.
The PlatformTransactionManager interface implementations normally require knowledge
of the environment in which they work, such as JDBC, or JTA or Hibernate and so on.
For JDBC, the implementation of PlatformTransactionManager is
org.springframework.jdbc.datasource.DataSourceTransactionManager
.
Spring Framework Configurations 69