Thanks, Tercio.  We're in a position with this project now where the
entire layer that handles interactions with Hibernate needs rewriting,
so guice-persist is a real option.  But I need to understand the JPA
better.

Can you help me understand why the Hibernate team prefers JPA?  Are
there any public blog posts or articles about their thoughts?

On Sep 15, 10:05 am, Tercio Filho <[email protected]> wrote:
> Basically, Yes, it means that Hibernate team prefers JPA...
>
> I don't totally agree with this affirmation, but, I do agree that
> using JPA is better in a long term...
>
> Anyway, I had a project that was entirely binded to Hibernate, and I
> needed to upgrade several libs but I couldn't because the new version
> of guice didn't support hibernate and then a lot of libs I couldn't
> update. I delayed it the most I could, two weeks ago I decided to go
> hands on and upgrade my entire project.
>
> It took me about a week, refactoring all my classes, changing my DAO,
> which was pretty straightforward by the way(I use a framework called
> GenericDAO,http://code.google.com/p/hibernate-generic-dao/which
> helped me a lot...) and understanding the differences between the JPA
> annotations and the Hibernate in my project, behavour ones.
>
> I was a little quaky about this whole change, but in the end seemed
> that this is the way to go.
>
> I don't know if your project is tied with other projects that are tied
> to Hibernate, but if you can do the change I guarantee that is
> appreciated...
>
> I also tried to develop my version of hibernate support to Guice-
> Persist, but the time it would consume doesn't worthy... instead I
> refactored my entire project and stick with the official version...
>
> Regards
>
> On Sep 14, 8:06 pm, Ryan <[email protected]> wrote:
>
>
>
>
>
>
>
> > We are going to be refactoring our DAO in the near future, and I'm
> > interesting in replacing our existing Spring-Hibernate solution with a
> > guice-persist-Hibernate solution.  I noticed that guice-persist only
> > supports Hibernate via the JPA, and Dhanji gave this as the reason
> > (see link below):
>
> > "The hibernate team themselves are also moving in this direction
> > [using EntityManager], so I felt it was the logical choice."
>
> > Can someone elaborate a little on what he meant by this?  Does he mean
> > that the Hibernate team prefers to have their API accessed via JPA?
>
> > Thanks,
> > Ryan
>
> >http://groups.google.com/group/google-guice/browse_thread/thread/c379...

-- 
You received this message because you are subscribed to the Google Groups 
"google-guice" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-guice?hl=en.

Reply via email to