We have a persistence framework used in conjunction with our business object foundation called eQ!. It follows the DAO pattern, and is similar to how JDO works, where you tell the object to save it self, but that work is delegated to a PersistenceManager. This PM can use any kind of persister plugged in. Obviously, SQL persisters are the most common, but we have also just created a persister that goes to EJBs, so the client tier can tell the object to save itself, and it will actually happen on the EJB tier.
Along with this we have built adapters for Struts that allow the use of only one ActionForm and Action class (via a scripting mechanism). We will be providing a download of this foundation (with the struts adapters and others) very soon. For more info, www.browsersoft.com/eQ or email me: [EMAIL PROTECTED] Robert McIntosh -----Original Message----- From: Struts Newsgroup [mailto:@[EMAIL PROTECTED]] Sent: Tuesday, January 22, 2002 5:25 PM To: [EMAIL PROTECTED] Subject: Model Persistence Survey Subject: Model Persistence Survey From: Vic Cekvenich <[EMAIL PROTECTED]> === I do not like surveys. But I would like to get a feel for "How are people implementing the model persistence". Sort of a popularity contest. Also if you did not like it, how would you do it next time. So if you would please respond. How do you implement model persistence to a SQL DB. EJB (even for non-midleware needed webapps) Expreso features JDBC ResultSet w/ own base class i Village /Tourge JDBC RowSet (http://download-west.oracle.com/otndoc/oracle9i/901_doc/java.901/a90211 /rowset.htm) Other? Is there another way? Right now I like RowSet, but what is popular out there? Currious, TIA Vic ps: maybe one day those "hooks" grow on Sturts, so Struts takes a stance on a good aproach for model persistance -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
