On Thu, 17 Feb 2011 06:14:29 -0200, Igor Drobiazko
<[email protected]> wrote:
I'm not sure if such a module is what Tapestry needs to cover.
Why not? This is something IoC packages end up implementing. I guess there
are some people using Spring with Tapestry 5 just for the transaction
management and they would be more than happy to get rid of Spring. I'm one
of them.
However, if we decide to provide such a module, I don't see it in T5.3.
Right now I
would like to concentrate on plain JPA support, which can be extended
by a transaction module later.
Agreed.
--
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: [email protected]
For additional commands, e-mail: [email protected]
