On Thu, 07 Oct 2010 15:34:36 -0300, Jeshurun Daniel <sjeshu...@yahoo.ca>
wrote:
Hi Thiago,
Hi!
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.
If you're talking about Spring beans, that's very strange. Are you sure
you used all the XML namespaces correctly? If you're talking about
Tapestry-IoC services, the Spring @Transactional doesn't reach there, just
objects instantiated by Spring itself.
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.
I've used Spring beans with @Transactional and <tx-annotation-driven> and
@Inject'ing them in Tapestry pages and Tapestry-IoC services with no
problems.
--
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
