On Mon, Jun 02,'03 (08:56 PM GMT-0400), Vic wrote: > Of course this fixed it: > <forward name="Saved" path="/do/chapterAction?Dispatch=edit" > redirect = "true" /> > but... as you say, be aware. > .V > (I would almost argue it's a bug..... but if it makes sense to you).
I'm not sure of the 'best' solution. I think everything has it's trade offs. Even with something like a search action forwarding to a display - the display action then becomes FORCED to have to be aware of a possible search action (and search bean) forwarding to it. That being the case, to me, I'm still not so sure that's it's "wrong" instead to have the search action, and resulting display be set up from the search action. To me it makes the search action be 'self sufficient' and even re-usable and keeps your other Action independent of having to care about the search action/SearhBean. BUT, if it makes more sense to have the one action forward to the other action, all is not lost... all that needs to be done is you have some logic in the forwarded to action (say ActionB) so that ActionB can reset the ActionForm that comes in from the forwarded request. The problem, though, is this breaks a lot of rules of Actions having to be aware of other Actions etc. Because of this, in most circumstances, I don't really like Actions forwarding to other Actions (because of the 'potential' problems that might occur). Maybe someone out there has a better solution? -- Rick _______________________________________________ MVC-Programmers mailing list [EMAIL PROTECTED] http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers
