I've managed to avoid Action Chaining all together. I worked recently with a company that has a framework they wrote that uses "processing pipelines" similar to cocoon. Having been a struts guy for 1 1/2 years now it was a little strange to put my mind on that track. But there implementation was great it worked solid. But, being that there framework was based on the "processing pipeline" it handled it well. Struts is not built that way by design. So, I like to avoid it.
So far I have been able to avoid it by creating Actions I can extend (which is a debate too) and using tiles which can call actions themselves for spin off actions that need to be called from the page and need no parameters to display it. I put together a whole article management system this way (http://www.joebasirico.com [work in progress]). Anyways, any of the flexibility that I saw in the "processing pipeline" I now see how it can be done via the struts way. Between Tiles, LookupDispatchAction and that handy struts-config file I can slap together a very functional site in only a couple hours (but it wouldn't be visually pretty). Brandon Goodin Phase Web and Multimedia P (406) 862-2245 F (406) 862-0354 [EMAIL PROTECTED] http://www.phase.ws > -----Original Message----- > From: Eddie Bush [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 12, 2002 10:12 AM > To: Struts Developers List > Subject: Re: Action chaining: (was - Re: Why are people up on Struts) > > > :-) Precisely. Everyone should certainly be aware of the possible > side-effects of chaining via a forward though. Assuming you realize the > possible problem there, and avoid it, you're fine AFAICT. If someone > has reason why this sort of chaining (the redirect type - not the > forward) is bad, I'd sure love to hear it ... but I'll probably wind up > using it anyway ;-O > > Edgar P. Dollin wrote: > > >My viewpoints are a little more simplistic. > > > >There is a lot of gray area between the definition of presentation layer > >and business logic. There has to be some impact or you couldn't drive > >the business layer from the presentation layer. > > > >We do the best we can to minimize the impact of one upon the other. If > >something is clear, i.e. the shape of the buttons is presentation layer, > >the layout of the tables is business layer, you put it in the correct > >space. If something is gray, i.e. frobnicatation, you understand it the > >best you can and break it up in a logical way. > > > >Lastly you use the tools available, with action chaining being one of > >the tools, to implement your analysis. If your analysis works best with > >action chaining, you are a winner, if it works without it, great too. > > > >Edgar :-) > > > > -- > 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]>
