Spring Training

Note how the TransactionProxyFactoryBean above is named gameRenter. This is because it will produce a transactional GameRenter implementation and that is what we want to expose to client code (not the raw business object.)

It is using FactoryBean.
The tutor emphasized that FactoryBean will return its producer.

AbstractTransactionalDataSourceSpringContextTests
It is very useful for unit test. It will help to re-instate the status of test database

Transaction
To implements declarative transaction, you can use AOP or AspectJ or something else.

For AOP, the logic flow is as follows:

Advisor -> Interceptor ->TransactionManager & transactionAttributeSource
TransactionAttributeSource -> MatchAlwaysTranstionAttributeSource | metadata.commons.CommonsAttributes

Hongfeng Sun : 11 Jan 2006 16:42 |  Tags: Spring-Hibernate-Jboss Training |  Comments (0) |  Trackbacks (1) |  Report a problem