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 :) regards Taha On Nov 30, 2012, at 4:07 PM, dreamer1212 wrote: > Hi lists, Sorry if this question has been asked or self-explain for tapestry > veterans. > What're the pros and cons of using tapestry-hibernate, I mean what will I > miss if I let spring handle all presistence for me, I don't want to lose the > ability to make my transaction declarative... > > Thanks > Douglas > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/newbie-question-on-tapestry-hiberate-tp5718412.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org >
