Re: new/update form patterns
Re: new/update form patterns
- Subject: Re: new/update form patterns
- From: Arturo Perez <email@hidden>
- Date: Fri, 27 May 2005 11:19:07 -0400
For me, I've a subclassed WOComponent that manages new EOs and a peer
editng context. That way if the user cancels I can just throw away the
whole thing. And I get to keep all the goodness associated with EOs in
an editing context.
When I identify a new EO that a user may need to create, I create the
WOComponent, change the extends WOComponent to my custom subclass and I
automatically get save, cancel, validation handling and peer editing
capabilities.
But that's just what I do. Do what feels right for yourself. Wonder,
for example, probably already has all of that built right in.
-arturo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden