> When I speak of Action chaining, I mean to say a scenario where one > action mapping's suggested forward path is not directly to a response > generator (a JSP), but in fact to another mapped action (which will > eventually forward to a response generator). I was advising against this > (I know the tempation is there -- I have done it myself) because it > causes all the dozen or so methods in the request processor "chain" to > be executed again, redundantly in most cases, and also somewhat because > of the "hidden" nature of the processing (which is also why I have > avoided some genuine Struts niceties so far, but, let's face it, a > strength of Struts is indeed declarative programming).
Ted, in my sample CRUD application i have editAction, which displays an item in HTML form. It takes item ID as parameter. This action is mapped, it can be called directly from a page using link, like editAction.do?ID=1234. Another way to call it is to call it from createAction, which creates new item, assigns in ID to it, and redirects to editItem with ID attached to the URL as query parameter. Is this chaining? This works great and allows to add a level of abstraction, so editItem does not know where the data comes from. This modularized approach allows to create application with high level of reuse. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
