+1
We've used hibernate pretty extensively on a number of projects, both
large and small, overall I've been very pleased with the results. You
are likely already aware of this, but the Spring community no longer
recommends using the HibernateTemplate and instead prefers a
template-less approach since the original reasons for the creation/usage
of the HibernateTemplate no longer exist.
Here is an article on the subject.
http://blog.interface21.com/main/2007/06/26/so-should-you-still-use-springs-hibernatetemplate-andor-jpatemplate/
Eric Dalquist wrote:
As I progress with the Pluto 1.1 integration in the trunk I'm getting
closer to the point of needing to write some new DAOs to persist some
portlet domain objects. I would like to propose using Hibernate 3 for
_new_ DAO implementations. Initially this just provides an easy way to
write DAOs for object persistence, in the very long term we could plan
on moving all DAOs to Hibernate to take advantage of schema creation
and cross-database support. For 3.0 Hibernate would only be used for
new DAOs and all existing data access code would remain as is.
-Eric
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
