|
> From: Ivan Hurtado > > I am in the infancy stage with this design, so I can > go in any direction. Using EJB is the major decision I > am still grapling with. I understand what you are > saying about using JDO for data access, however, what > about all the other system level functionality that an > EJB server/container provides... i.e. the connection > pooling, thread mgmt, session/state mgmt, etc? I'd > rather not code any of that. You really should take a look at some of the other ORM packages available. Hibernate is a good place to start: www.hibernate.org Here's a nice discussion on JDO vs. EJB/CMP: http://www.caucho.com/support/resin-interest/0308/0143.html And there's another great place for discussing persistence here: http://213.190.42.244/whisper/space/Persistence+frameworks I'm in no way an expert on this stuff. I suggest you take your time to do some homework, read the threads. I like to use Google and search on things like "EJB vs. JDO" or "EJB nightmares" or "Hibernate problems" and find out what people really think. I don't mean to completely diss the EJB architecture; there are benefits to EJB for some sites like Amazon.com, where they may have failover among dozens of machines. That might be what Dieter refers to as "scalability". But for single-machine use (as is typical on an iSeries), the EJB model is definitely overkill. Joe
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.