On Sun, 2011-01-02 at 23:47 -0500, Eric B wrote: > > Thanks for the tip. That's kind of what I was looking for. Ideally, > the great thing about Struts2 is that you can also put the action to > take based on the result in a config file, which completely separates > the workflow from the action. In symfony, the way I see it, the > action needs to know something about the workflow (ie: if came from > route A, redirect, if route B, display template, if route C, chain > another action, etc...). Which ties the action to the workflow. What > I would have loved to see is a config file similar to the routing yml > which would inspect the result from the action, and determine what the > next step would be. If we managed to contain everything in one file, > it would be awesome.
This is what filters do. Filters are executed before and after an action(That is, filters execute, the middle filter - execution, runs the action, renders the view, and so on). You can put a filter just after execution(or modify execution, depending on what you need), which does the redirect based on the action's results. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
