|
Hi, In a new, OO Java App that will be running on WAS using DB2 on iSeries, what is the prefered way to manage persistence? Is it a given to use an ORM product? To write your own beans? To use JDO? EJB's? ... I've searched the Java400-L archives and found some info, but I thought I'd ask my fellow green-screeners as well. All of the above seem like overkill to me, but my Java gurus say they want separation between the OO programs and the data handling (including dirty bit detection, connection pool handling, commitment control, etc). Any general opinions appreciated. TIA. --Chapin Kaynor Vermont
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.