There are few 'trends' that "most" in the community seem to agree on.
Eclipse was the first I noticed in this community.
Hibernate and Spring were the second and third (not sure the order). I
don't think you'll find much dissension on using Hibernate.
But.... If you really wanted to open the door and think about all the
reasons why or not, to use Hibernate, there is one downside.
RedHat/JBoss and Interface 21 do not get along. I get the impression
that some people use iBatis not because they think it's better then
Hibernate, but because of the riff here and a desire to use something
"other" then Hibernate.
Personally, I'd use Hibernate. +1.
---- Cris J H
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
