I can apply some real-world examples here: I'm in a screen that is updating document metadata, and the form submits to UpdateMetadata.action. But UpdateMetadata.action is actually an alias for a complex chain:
ValidateMetadata -> BeginTx -> StoreMetadata -> CommitTx -> StoreMetadataInHtmlFiles -> LoadMetadata -> showmetadata.jsp And of course, if any of those have errors, they either end up at editmetadata.jsp directly or (in the case of StoreMetadata.error) to RollbackTx -> editmetadata.jsp. I really think a lot of AOP design ideas could be applied here I'm sure. -Pat ----- Original Message ----- From: "Rickard Öberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 30, 2002 7:39 AM Subject: Re: [OS-webwork] Rethink > boxed wrote: > >>* Chaining. IMHO this needs a big rethink, and most of all we need to > >>check: what are the usecases to be implemented. > > > > What would be an alternative way of doing chaining? Your example where the > > chaining is done in code and is specified by the action itself is just not > > acceptable for me, > > What example? > > /Rickard > > -- > Rickard Öberg > [EMAIL PROTECTED] > Senselogic > > Got blog? I do. http://dreambean.com > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
