> > 3) The object has been created and registered with a data
> context, but
> > not yet committed. I would suggest that best practices dictate this
> > use case never be exercised....
>
> I second the motion. A while ago I tried the approach of
> creating and registering a DataObject in my page's setup, but
> I never could get it to work completely right. If the user
> changed his mind and back-buttoned to a previous page, it
> left an uncommitted object in the DataContext. I think the
> Refresh button wasn't too kind either. I finally gave up on
> that approach.
>
We had similar problems. To make it worse, it ended up creating a huge
coupling between the view and the service layer. This approach only seems
worthwhile to me when you have an established persistence layer (ala EJB,
etc) in your application.
Cris
This archive was generated by hypermail 2.0.0 : Mon Apr 04 2005 - 13:10:28 EDT