> 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).
For search-related issues, you might want to look at Compass [1]. For data partitioning, you might want to take a look at the OpenJPA Slice subproject, which Pinaki Poddar developed and recently contributed to the OpenJPA trunk. [1] http://www.compass-project.org/ -Patrick On Thu, Feb 28, 2008 at 6:36 AM, Darren Hartford <[EMAIL PROTECTED]> 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 > > > > > -- Patrick Linskey 202 669 5907
