RE: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

Hi Ted, This explanatation has set to rest most of my doubts about action chainning..And I think the way Most of us use actions(One action to serve the request like save action)and another to display the page (like getAccountsList Action )is not action chainning but action relay which is

Re: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

Hi, I agree with u that u can have another layer of abstraction(like helper beans) between action and Service layer.So that same code ecan be reused. But this some disadvangates. Firstly U are then not really using the power of Struts Configuration file which allows you to use logical mappings

RE: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

Hi, Does this mean that using action forwards To point another action is not action chainning?So we can call this action relay and its in line with Struts design principles? And as u said,We have really abstracted away all error handling etc to Abstract Action class.But the point is if we go

RE: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

Ted, can you (or someone else) clarify the difference b/t action chaining and action relay? Thanks, Greg -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 5:34 AM To: [EMAIL PROTECTED] Subject: RE: design question about action

Re: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

We think Struts power lies in its simple and rigorous design process. If you combine Struts-Tiles, you will have the display Action for the whole page and actions for all included tiles. Actions are controllers that can have parameters set in the configuration file. With careful design of helper

RE: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

Ted, will you give me your opinion on my post of Mon 1/27/2003 5:21 PM with a subject of RE: Two ActionForms colliding on property name? I am wondering whether you see my splitting of actions into post-actions and pre-actions as action relays or action chaining. To use the input attribute in

design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

Hi All, I have a very basic design question about struts action design..We have been developing a fairly large and complex web application involving struts and struts has proved to be a great help :-)) But after reading the book by Mr. Husted et al., Struts in action,I have some basic

RE: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

You've stated it correctly when you said that Actions are your flow controllers. In the case of your login/getAccounts example, you should have a business object that handles login, and a business object that gets accounts. You would then have a login action (use case controller) that would

Re: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

We achieve what you describe as a chain of actions for re-use with helper beans and follow Struts design principal as Ted described. The helper beans can be ready in cache or service pool for reuse. Look at http://myportal.myb2cb2b.com/com.dbgroups.ppf/model/web/dao.html Hope this may help.

RE: design question about action chainning(As quoted in :Struts in action...by Ted Husted et al..)

But you still have to duplicate code in the actions, right? Even if that code is as simple as: Service service = Service.getService(SERVICE_KEY); Foo[] foos = service.getFoos(); request.setAttribute(FOO_KEY, foos); Action chaining allows this code to be written once and used many times. Thus