On Fri, 30 Nov 2012 09:59:47 -0200, Taha Siddiqi
<tawus.tapes...@gmail.com> wrote:
In my view
PROS :
1. Simple:- add dependencies, write a hibernate.cfg.xml and put it in
your resources directory and you are done.
2. Done tapestry style, you can inject Session into pages, components(I
know bad practise) or services.
3. Minimum configuration
CONS:
1. Tapestry can handle only one SessionFactory.
2. Declarative transaction support is minimal, just @CommitAfter. But
you can always extend it :)
Do you really need more complex transaction handling? @CommitAfter is the
same as the 'required' option in Spring's @Transactional. If you don't, go
with tapestry-hibernate, as it's already integrated and easier to use (not
to mention that the IoC part of Tapestry is better than Spring's).
Otherwise, go for spring-tx.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
