Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin3!goblin.stu.neva.ru!newsfeed3.funet.fi!newsfeeds.funet.fi!fi.sn.net!newsfeed2.tdcnet.fi!news.song.fi!not-for-mail From: Jukka Lahtinen Newsgroups: comp.lang.java.programmer Subject: Re: Spring/hibernate and JDBC Organization: none References: <3c16e5e7-3c0b-4126-9dd9-88f372a58f03@e26g2000prf.googlegroups.com> X-no-archive: yes Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: 8bit Date: Mon, 11 Jul 2011 09:52:46 +0300 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:siz3HBE5C0I0xCP3Zt/cF5YtpjQ= MIME-Version: 1.0 Lines: 20 NNTP-Posting-Host: 81.17.207.67 X-Trace: 1310367316 news.tdc.fi 2856 81.17.207.67:52154 X-Complaints-To: abuse@tdcnet.fi Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6067 Jack writes: > With spring and hibernate so popular now, is there anybody still only > use JDBC to write database application code? Thanks. Yes. I'm maintaining a large application that has all the database access done with jdbc, mainly for historical reasons. The application has been in production since the beginning of 2004, and at some early point of the implementation project (about 2001 or 2002) people experienced some problems with entity beans not always being saved to the database in the correct order (or something like that, it was before I got involved) and decided to switch to raw jdbc. That was the days of Java 1.3 and ejb 2.1. If the application were to be rewritten today, we would probably use hibernate or something. -- Jukka Lahtinen