Re: Spring/hibernate and JDBC

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Thu, 21 Jul 2011 18:02:52 -0400

Message-ID:

<4e28a20f$0$309$14726298@news.sunsite.dk>

On 7/10/2011 8:24 AM, Stefan Ram wrote:

Jack<junw2000@gmail.com> 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?

Yes.

It works fine.

Working in SE context was one of the design goals behind
entity beans -> JPA as far as I remember.

   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).

Today it is common to need 20-30 different open source libs.

Just a mental barrier to get over.

   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!

Could make sense.

Arne