Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe08.iad.POSTED!8ad76e89!not-for-mail From: Arved Sandstrom User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 Newsgroups: comp.lang.java.programmer Subject: Re: Spring/hibernate and JDBC References: <3c16e5e7-3c0b-4126-9dd9-88f372a58f03@e26g2000prf.googlegroups.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Lines: 36 Message-ID: X-Complaints-To: abuse@newsgroups-download.com NNTP-Posting-Date: Sun, 10 Jul 2011 13:44:45 UTC Organization: Public Usenet Newsgroup Access Date: Sun, 10 Jul 2011 10:44:41 -0300 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6044 On 11-07-10 09:24 AM, Stefan Ram wrote: > Jack writes: >> With spring and hibernate so popular now, is there anybody still only >> use JDBC to write database application code? Thanks. > > I like the idea of JPA, but AFAIK, no implementation is part > of Java SE? So the canonical way to develope a desktop > application with JPA would be to mix Java SE with a database > and a JPA implementation? > > I dislike to depend on too many different libraries and > providers (i.e., Java SE is provided by Oracle, Hibernate by > another party, the database possibly by another party). FWIW, Stefan (and you likely know this), Oracle has EclipseLink as a JPA implementation. And it's the reference implementation as well. All that matters to me is that the Java Persistence API is in javax.persistence, and it's considered to be a framework for _both_ J2SE and J2EE/Java EE. That's standard enough for me. I in fact prefer that the actual implementation decision is not made for me by bundling. > I am disappointed that Derby is only part of the JDK, but > not of the JRE. I surely would love Derby and an JPA > implementation to be part of Java SE! > What do you gain? The persistence API is standard after all. And are you sure you'd want to have either Hibernate or OpenJPA or EclipseLink (among others) hardwired into the J2SE distro? If Hibernate, for example, were included, *I* wouldn't be all that happy, but many others would be pleased. If EclipseLink were bundled, I'd be happy, but others would be displeased. I see no win-win here. It's exceptionally easy to include any of the common JPA implementations. AHS