On Thu, Feb 19, 2009 at 5:23 PM, Thiago H. de Paula Figueiredo < [email protected]> wrote:
> Em Thu, 19 Feb 2009 17:13:30 -0300, Marcelo Lotif <[email protected]> > escreveu: > > No, I don't. I suppose it's lighter because to integrate toplink+JPA you >> only have to download 2 jars, something like 5mb.When I tried to switch to >> hibernate+JPA, I have to download a LOT more dependencies than toplink, >> > > I thought you were talking of "lightweight" like they say Spring is lighter > than EJB 2.x. :) > Hibernate has more features than JPA, so it should have more code. > Regarding number of dependencies, Maven takes care of that to me. :) > Well, when i first tried hibernate+JPA I was into Tapestry 4 and then there was no maven. There was really difficult to integrate them 3, specially because I had a previous experience with toplink. Since then, I have personal bad feelings with hibernate. Nothing really reasonable. And about the performance, I really don't have any clue about who's faster :) > > > plus the dificulty of the process itself and the lack of documentation. >> > > What process? Lack of documentation? Hibernate has one of the best > documentations I've seen in open-source projects. And it does almost > everything JPA does, using the same annotations and defaults, so I guess a > JPA -> Hibernate transition should be easy. AFAIK, besides the JPA > listeners, Hibernate is a proper superser of JPA. > > seraching a little, I read somewere that toplink was a project made to >> provide an easy JPA implementation, so that is the reason. >> > > Being JPA a standard, I guess all implementations should be as easy to easy > as each other . . . at least in theory. :) > > To add some more advantage to toplink, I found a pretty useful "annotation >> reference" guide that's better than anything I ever found into hibernate >> documentation on the internet. >> > > That's exactly the reference I use and the one I recommend to everyone. ;) > > Since hibernate annotations are pretty much >> the same as toplink/JPA, >> >> http://www.oracle.com/technology/products/ias/toplink/jpa/resources/toplink-jpa-annotations.html >> > > Hibernate uses all the JPA annotations exactly like JPA does. In fact, > Hibernate's own annotations are just used to deal with features Hibernate > has and JPA doesn't (@CollectionOfElements, @BatchSize, etc). No Hibernate > annotation overlaps JPA's ones (besides cascading options). > Well, I think we are heading to something outside this list intentions! This is what I think: if there's sufficient people who cares about a tapestry-jpa integration to justify the effort of doing it, that must be done! And with one more person in the tapestry team, it will be 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
