Thanks Taha and Thiago, sounds like I should embrace tapestry-hibernate for
handy projects.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/newbie-question-on-tapestry-hiberate-tp5718412p5718436.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
On Fri, 30 Nov 2012 09:59:47 -0200, Taha Siddiqi
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 service
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