Hi, I had some experience with both tapestry-hibernate and tapestry+JPA, and it was something like this:
I thought hibernate was too complicated, but I was used to it When I met JPA+toplink, I put it into my tapestry applications and I thought it was easier than hibernate 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 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? On Wed, Feb 18, 2009 at 12:28 PM, Thiago H. de Paula Figueiredo < [email protected]> wrote: > On Wed, Feb 18, 2009 at 12:16 PM, Dmitry Gusev <[email protected]> > wrote: > > Hi, Thiago! > > Hi, Dmitry! > > > I've implemented my own lightweight API providing ORM/JPA functionality > to > > tapestry application. I've just published the library sources here > > http://code.google.com/p/keyintegrity-orm/ > > I'll take a look at that. :) > > -- > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Marcelo Lotif
