Creating branch for execution flow remodeling
work in progress: new execution flow, action stack is gone, decoration doesn't require special abilities of the renderer anymore, but still needs further abstraction. decorators in decorators (for slots) should work now, and slots are available in the main content template. also, caching for execution filter is in place, albeit not enabled/complete yet. refs #298, #302, #212 and #215
more renderer cleanup
oops
threw out action stack completely, made execution container factory configurable, refs #298, #215
allow setting max forwards to '0'
removed some docs references to rendering filters
more execution flow cleanup, refs #298, #215
exception catching fix
oopsie
fixed tests
fixed action instance being created too early
#298 and #212: more work on execution flow, implemented the new layered rendering system. upcoming awesomeness: we'll have (optionally) configurable layouts, and the necessary changes for that will allow to have other template sources than just the file system. enjoy, and test this please (some parts are still rather wonky and have to be figured out, but it works in general)
disabled output type setting from routing.xml in sample app until the routing is changed to create the first container and thus gets access to an output type object
more work on execution flow changes, next works now again, security filter forwards etc have been figured out. we still have to eliminate some of the wonkiness with the global response, that's gonna be rather difficult, I imagine. refs #298
merged in changes from trunk, revisions a96d71abff3b9c85693c6e1db1fd7414f677fa4d to 26fd3d7517d5c224540c3a57fffd13816f267c7a
make the scope of exception templates a little less cluttered up with random variables
more execution flow refactoring: removed merge/export/import/lock nonsense from responses. execution containers can now be created with an output type, forwards done now by returning an array from the view instead of an exec container (not sure if we'll keep that). slots and global response stuff todo. refs #298
first take on response merging stuff, refs #298
Introduce Agavi(Web)RequestDataHolder for storing request data (post/get parameters, cookies, files, ...)