So is it a bad design if you have Action1 -> add CollectionOfObject1 to request Action2 -> add Object2 request
And then chain them together to produce two request attributes? I have some pages which display a list of Object1, and other pages which require the Collection to populate a select. So I define action path 1 to be action 1 and forward to the display for the Collection of Object1, and define action path 2 to be action 1 forward to action 2 forward to editor page which has a select of collection of object 1, while editing Object2. Thanks, Tim > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 31, 2003 4:04 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: Problem with action chaining > > > Hi , > As pointed out by Mohan, Action chainning is not a good > design practice... You can forward from one action to another > but they should eb performing completely independent units of > work.If two actions are used to complete only bits of work to > complete one logical response, then it is a bad design. There > is a discussion thread about action chainning in mail archive. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
