Ok, Eddie, I do the same :) What I was mean there are many code uses DAO pattern to create services that retreive objects from database, but no services for store objects.
I do two services, one for retreive objects, another store objects. That�s because retreived objects in my web-app, is more frequent that store ( basically only administrator can create/store objects -users, groups, catalogs- and clients log-in and consult catalogs). I�ve used the same that Chuck�s book, views/databse objects to decouple the service. And works fine!. I�ll like to see code for other developers to learn. I�ve used DAO patterns whit ODMG. It works without problems!. I don�t understand why, in another thread, was saying ODMG was not suitable for DAO. Greetings -----Mensaje original----- De: Eddie Bush [mailto:[EMAIL PROTECTED]] Enviado el: viernes, 11 de octubre de 2002 7:08 Para: OJB Users List Asunto: Re: Chuck Cavaness's Beer4All App Hi Jose, The way I do this is carry the PK as a hidden field in the form. Then, when it submits I query to get the original object (I build an example object using the PK I sent myself as a hidden field and do a QueryByCriteria), update it's values, and then store it again. Someone else may have a better way -- but that works fine for me. This is a good example of why PKs should have no special business meaning :-) (it will be publicly visible) Jose Galiana wrote: >By the way, > >I�ve noticed there are many samples for retreive objects from DB, but no >samples to store objects and collection to work with WEB-apps. > >Are there any sample for that? > >Thanks >Jose Galiana > -- Eddie Bush -- 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]>
