Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.glorb.com!news-spur2.glorb.com!homer.glorb.com!.POSTED!not-for-mail From: Steve Sobol Newsgroups: comp.lang.java.programmer Subject: Re: Hibernate Date: Wed, 4 May 2011 13:19:47 -0700 Organization: Glorb Internet Services, http://www.glorb.com Lines: 29 Message-ID: References: NNTP-Posting-Host: xoAFiuXnRqdiUJrjkwExXQ.user.posting2.glorb.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@glorb.com NNTP-Posting-Date: Wed, 4 May 2011 20:19:48 +0000 (UTC) User-Agent: MicroPlanet-Gravity/3.0.4 X-Notice: Scanned by Mr. Bill Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3513 In article , Arved Sandstrom says... > Let me make one recommendation, Steve. Especially given that you have > used Hibernate before, and some time ago. Try not to use Hibernate > native APIs - stick to JPA. At least in a Java EE environment. I'm not a > Hibernate guy any more - haven't been since the first few years after it > came out - but I see that since 3.5 Hibernate has had JPA 2 support, and > I'd expect that by now it's in pretty good shape. Yes. Most of what I'm using consists of JPA native APIs, judging by the number of javax.persistence imports compared to org.hibernate imports. :) > Why use JPA at all? It's standard. It simplifies your reasoning about > persistence. Considering that there will still be plenty of need to > think about caching strategies, and persistent object lifetimes, and > query optimization, and object relationships, and lazy loading - in any > API and implementation that you choose - it's not a bad idea to > standardize and simplify what you can. > > My 2 cents worth. FWIW I agree completely. -- Steve Sobol - Programming/WebDev/IT Support sjsobol@JustThe.net