Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!news2.arglkargh.de!nuzba.szn.dk!news.szn.dk!pnx.dk!dotsrc.org!filter.dotsrc.org!news.dotsrc.org!not-for-mail
Date: Thu, 21 Jul 2011 17:55:38 -0400
From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
Newsgroups: comp.lang.java.programmer
Subject: Re: Spring/hibernate and JDBC
References: <3c16e5e7-3c0b-4126-9dd9-88f372a58f03@e26g2000prf.googlegroups.com> <ivamk9$dph$1@dont-email.me> <5094c9a2-2a80-413e-8bca-8955861502d2@q12g2000prb.googlegroups.com>
In-Reply-To: <5094c9a2-2a80-413e-8bca-8955861502d2@q12g2000prb.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 28
Message-ID: <4e28a05e$0$316$14726298@news.sunsite.dk>
Organization: SunSITE.dk - Supporting Open source
NNTP-Posting-Host: 72.192.23.157
X-Trace: news.sunsite.dk DXC=4=B<hXafdaPD]J=fIXJe6_YSB=nbEKnk[XjhVkob8B`VJPe3\kP5EUQKBm9cfh9BSTM2;kT<[:>[Q>fLY05<E>eT_>@TPG=BiQW
X-Complaints-To: staff@sunsite.dk
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6365

On 7/9/2011 8:29 PM, Jack wrote:
> On Jul 9, 4:01 pm, markspace<-@.>  wrote:
>> On 7/9/2011 2:56 PM, Jack wrote:
>>
>>> With spring and hibernate so popular now, is there anybody still only
>>> use JDBC to write database application code? Thanks.
>>
>> I'm sure someone is, but yes I assume that JPA&  Hibernate and
>> dependency injection frameworks like Spring and JSF have become the norm.
>>
>> Still good to know what JDBC is and does, since it's used by JPA and
>> Hibernate (et al.).
>
> What are the pros and cons of using Spring/hibernate and JDBC?

ORM (incl. Hibernate) provides you with an OO view that fit well
with an OO language like Java and you save a ton of trivial
code.

JDBC supports types of database access that are not object oriented
and are in general easier to follow regarding what is going on.

If the database access is  object oriented then I will recommend
using ORM and if necessary get the developers properly trained.

Arne