add another bean definition for the advice: and then for all objects that require transactionality, wrap the existing beans in a ProxyFactoryBean, which will apply the transaction advice: transactionAdvice Now all methods on the 'imageprocessor' bean will be called in a transactional context. Note, however, that they will not necessarily be called in their OWN transactional context, as nested and/or reentrant calls will inherit the transactional context of the outer/parent invocation. If you just need to make selected methods transactional (rather than all of them), you can use a NamedMethodPointcutAdvisor or a RegexMethodPointcutAdvisor to do so. By default, ColdSpring uses a DefaultPointcutAdvisor (which matches all methods) when one is not explicitly configured. If you would like to monitor the transactional method call stack, you can uncomment the five CFTRACE tags inside the invokeMethod method that indicate when a transactional method is entered or exited (including whether it was nested or not and whether it completed normally or raised an exception). This component has only been tested with the current CVS version of ColdSpring (as of July 15, 2008). ------------------------------------------------------------------------ $Id$ Copyright 2008 Barney Boisvert (bboisvert@gmail.com). Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --->