spring集成struts事务处理

要在项目中添加声明式事务处理，但是由于开发前期没有很好的规划。很多业务都已经直接写在了action这一层了。service层几乎没写。所以就只有在action层添加事务了。但是添加的事务对于dispatchAction无效。查看代码发现，dispatchAction的所以方法都是通过execute()调用。而spring的声明式事务处理，是通过TransactionInterceptor类来进行拦截调用的。

java 代码

public Object invoke(final MethodInvocation invocation) throws Throwable {
        // Work out the target class: may be <code>null</code>.
        // The TransactionAttributeSource should be passed the target class
        // as well as the method, which may be from an interface.
        Class targetClass = (invocation.getThis() != null ? invocation.getThis().getClass() : null);

        // If the transaction attribute is null, the method is non-transactional.
        final TransactionAttribute txAttr =
                getTransactionAttributeSource().getTransactionAttribute(invocation.getMethod(), targetClass);
        final String joinpointIdentification = methodIdentification(invocation.getMethod());

        if (txAttr == null || !(getTransactionManager() instanceof CallbackPreferringPlatformTransactionManager)) {
            // Standard transaction demarcation with getTransaction and commit/rollback calls.
            TransactionInfo txInfo = createTransactionIfNecessary(txAttr, joinpointIdentification);
            Object retVal = null;
            try {
                // This is an around advice: Invoke the next interceptor in the chain.
                // This will normally result in a target object being invoked.
                retVal = invocation.proceed();
            }
            catch (Throwable ex) {
                // target invocation exception
                completeTransactionAfterThrowing(txInfo, ex);
                throw ex;
            }
            finally {
                cleanupTransactionInfo(txInfo);
            }
            commitTransactionAfterReturning(txInfo);
            return retVal;
        }

上面贴出的是主要的代码。可见它是通过对代理类的制定调用方法来进行事务管理。而dispatchAction的所以方法都是通过execute()调用。所以只有拦截其execute方法事务处理才有效。