You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by dreamer1212 <on...@yahoo.com.hk> on 2012/11/30 11:37:07 UTC
newbie question on tapestry-hiberate
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: newbie question on tapestry-hiberate
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 30 Nov 2012 09:59:47 -0200, Taha Siddiqi
<ta...@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: newbie question on tapestry-hiberate
Posted by Taha Siddiqi <ta...@gmail.com>.
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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
Re: newbie question on tapestry-hiberate
Posted by dreamer1212 <on...@yahoo.com.hk>.
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org