On Thu, Feb 19, 2009 at 4:38 PM, Thiago H. de Paula Figueiredo < [email protected]> wrote:
> Em Thu, 19 Feb 2009 16:25:35 -0300, Marcelo Lotif <[email protected]> > escreveu: > > and when I met tapestry-hibernate, I thought it was even easier that JPA, >> and as a plus has some features that just hibernate has, like criteria >> > > Criteria queries rules! > > Maybe is just a lack of knowledge, but I don't see any advantages of a >> tapestry-jpa module over the existent tapestry-hibernate, except the fact >> that toplink is lighter (and maybe faster) than hibernate. Can someone >> point me some? >> > > I guess the point is to support JPA for the people who wants pure, > non-Hibernate, JSR-starndard EntityManager-based ORM. And which one is > better is not something that everyone will agree. You're 100% right, but I thought there were deeper reasons for doing it, like some gain in performance or some missing functionality. > I'm on the Hibernate side, though. :) Like you pointed out, that's definitely a matter of taste! I'm just using tapestry-hibernate because it made the ORM thing a bit easier. :) > > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Marcelo Lotif Sent from: Rio de janeiro Rj Brazil.
