Thanks for your reponses... you may want to put them on the forum
http://java.dzone.com/news/hibernate-best-choice
Just so in the future when someone does a google search, they will get your
reasons for using OpenJPA.....
:o)
----- Original Message -----
From: "Gil Markham" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, February 28, 2008 9:31 AM
Subject: Re: Why would I choose OpenJPA over Hibernate?
The biggest advantage of OpenJPA (IMHO) is when you combine a complex
object model, fetch groups and a reflection based serialization engine
(JAXB,Xstream). The ability to have the orm layer grab exactly what the
application needs and then hand the model objects directly to a
serialization mechanism removes a serious amount of code devoted to
walking object graphs and using 'initialize'. If you are dealing with
simple databases and flat model classes there's little difference. As soon
as you're dealing with multiple levels of one-to-many relationships the
benefits of fetch groups become apparent immediately.
-Gil
Darren Hartford wrote:
I can definitely contribute to this conversation from the Hibernate
standpoint. I use hibernate in production for most of my scenarios --
however, there are open JIRA bugs that quite a few of us still have open
(up to a year or more?) and still have not been addressed.
For me specifically, pure orm.xml support is horrible in Hibernate, I've
had to do some workarounds to avoid using annotations. It should be a
choice, not a hack.
The one area I'm not familiar with is the instrument versus
non-instrument (sorry if my terminology is off) between different JPA
implementations.
Hibernate legacy support, as Adam mentioned, is not very good, but it
definitely holds up well on it's own and they are constantly innovating
in the direction that I personally want to see (hibernate search,
hibernate shards, etc).
My two coppers -- and I'm on your list because your reversemappingtool
kicks the butt off hibernate's for orm.xml support ;-)
-D
-----Original Message-----
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 28, 2008 9:22 AM
To: [email protected]
Subject: Re: Why would I choose OpenJPA over Hibernate?
I would use OpenJPA every time for the same reason as Brill. I started
off
my
current project with OpenJPA, but came across some bugs which are
show-
stoppers
for me.
Native Hibernate is also notoriously bad for legacy integration. When
I
plugged
in HibernateJPA, I had to make some changes to my mappings, changing
some
stuff
that was legitimate JPA as far as OpenJPA and Toplink were concerned.
But
Hibernate wouldn't have it. I often get the impression that Hibernate
is
heavy
on convention, and the convention is what Hibernate dictates ;)
Hands up if Hibernate ever fixed a JIRA that you raised? I had a
couple of
Jiras
I was very interested in. They were either closed down with 'invalid'
or
just
ignored.
Brill Pappin on 20/02/08 14:41, wrote:
I've used Hibernate extensively for many types of projects.
Once I got through the learning curve for OpenJPA I never went back.
Why?
Because I can do away with all the extra crap Hibernate has to have.
Maintenance is easier, etc, etc.
Thats not to say Hibernate is not a good technology, its fairly
mature,
but I like that all I need is a few annotations to make OpenJPA
work.
- Brill Pappin
Rick Hightower wrote:
http://java.dzone.com/news/hibernate-best-choice
Has anyone done a comparison of Hibernate versus OpenJPA that
compares
ease-of-use, caching, tool support, legacy integration, etc.?
Perhaps
such an internal report was used to decide which ORM tool to pick.
If
so, what were the results?
http://java.dzone.com/news/hibernate-best-choice
