Re: [cinjug-users] Hibernate and database default values

["Edward Sumerfield" <esumerfd@xxxxxxxxxxx>]

EJB 3 is based on hibernate. Can't get a better argument for dumping the
middle layer than that, from a reliability and benchmark perspective.

Spring will slow the construction of objects down but you gain maintenance
advantages. So the choice to use it should be more a comparison of what you
want to use it for that how fast it is.

Arguments against EJB should be based on time to market and maintenance
costs. Having said that, EJB3 is supposed to solve a lot of the overhead
problems so being in an EJB environment now puts you in a good position to
migrate when implementations are commonly available.

Personally, I would not choose an EJB environment if I didn't have to. There
is no reason for adding an additional network layer when a function call
layer is equally good.

Looking for a good counter argument... anyone?

----- Original Message ----- 
From: <twcrone@xxxxxxxxxxxxx>
To: "Bill Manuel" <bill.manuel@xxxxxxxxx>
Cc: "Chris Nelson" <cnelson4eii@xxxxxxxxx>; <users@xxxxxxxxxx>
Sent: Tuesday, July 26, 2005 9:11 AM
Subject: Re: [cinjug-users] Hibernate and database default values


> Hey,
>
> I am just starting to learn about how to use Hibernate on a relatively 
> small
> project with very low usage.  However I am interested in trying to gain 
> some
> momentum in my organization (government) to move toward lightwieght
> technologies like Spring and Hibernate and away from EJB.  Does anyone 
> know of
> some good benchmark implementations of Hibernate (and Spring) where the
> technologies are used for large enterprise applications with success.  I 
> need
> some examples (possibly other government organizations/agencies) to 
> justify
> the endeavor.
>
> Thanks,
> --
> twcrone@xxxxxxxxxxxxx
> 859-278-9634