One thing to check is that the interface used by your manager extend the generic manager interface (or declare all the methods you want to make transactional). It is worth noting that the advice is applied on the basis of the interface and not the implementation. In these cases I always find the stack traces useful in terms of working out which aspects have been applied.
Mike. On 10/31/07, Daniel Kibler <[EMAIL PROTECTED]> wrote: > > > I'm still plagued by this issue. It's the same if I'm doing jetty:run or > jetty:run-war. I still cannot save any objects that use their own Manager. > I > found the statement below about transactions for managers in the Service > Tutorial. Could it be that this adviceis not happening for my managers? > > Transactions > All service.*Manager beans will automatically be configured by Spring to > wrap PROPOGATION_REQUIRED transactions around their method executions. > This > is done by the following Spring AOP configuration in appfuse-service.jar. > > <aop:config> > ... > <aop:advisor id="managerTx" advice-ref="txAdvice" > pointcut="execution(* *..service.*Manager.*(..))" order="2"/> > </aop:config> > > > -- > View this message in context: > http://www.nabble.com/Data-Access-Failure-tf4708700s2369.html#a13510596 > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
