Hi Thiago, Thanks for the quick reply. I know this is the pre-spring 2.0 way of doing things and <tx:annotation-driven> is the way to go, which was is my question. When i do things the old way, they work fine, but when I use <tx:annotation-driven>, it doesn't work, the proxy never gets created for the service class. I was wondering if it had something to do with the way I was injecting the service into my page class, or the way Spring's applicationcontext is created in Tapestry (maybe it needs additional configuration to support annotation-driven transactions), which is why I posted it here. Thanks again,Jeshurun --- On Thu, 10/7/10, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote:
From: Thiago H. de Paula Figueiredo <thiag...@gmail.com> Subject: Re: @Transactional annotation driven transactions in injected services - Proxy not created To: "Tapestry users" <users@tapestry.apache.org> Received: Thursday, October 7, 2010, 1:10 PM On Thu, 07 Oct 2010 15:05:58 -0300, Jeshurun Daniel <sjeshu...@yahoo.ca> wrote: > Hello everyone, Hi! This is a pure Spring question, but I'll anwer: use Spring 2.5+'s <tx:annotation-driven>, not TransactionProxyFactoryBean, which is the way older way of dealing with transactions. --Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
