|
My position on EJBs has not changed since the late 90's <grin>. The issue is larger than that, however. Your persistence architecture should not have any effect on your overall application design. It should be transparent to the application programmer. I think you should have business objects that talk to servers which in turn talk to an implementation layer, and that layer should be "plug and play", allowing you to use whichever database implementation best suits you. If your choice of persistence changes your application design, then you application needs a new design. Joe > From: Bartell, Aaron L. (TC) > > Are EJB's the way to go or should other technologies like Hibernate and > the like be used if those meet your needs? > > I know this has been debated before, and the reason I am asking it again > is to get time sensitive opinions in case they are different from a year > ago.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
