Hi everyone,

request methods can now be per-container. Should greatly reduce the  
pain when you embed slots that are also used as "normal" actions, just  
with a different layout, in sidebars or something, where their  
executeWrite() would be called if you submit a form in the "main"  
content area and a post request occurs:
- By default, all newly created containers use the global request method
- AgaviController::createExecutionContainer() now has a new argument  
for the request method
- AgaviExecutionContainer::createExecutionContainer() (and thus  
AgaviView::createForwardContainer() and  
AgaviView::createSlotContainer()) copy their own request method into  
the newly created containers (just like they do with the output type)
- In output_types.xml layout definitions, you may now use <slot ...  
method="read" /> to conveniently force a request method for a slot.

As always, the ticket (http://trac.agavi.org/ticket/667) and  
CHANGELOG / RELEASE_NOTES have more info.

Play around with it and let us know what you think!

Also, we've removed AgaviValidator::validatesInMethod(), the  
associated checks, and the passing of a request method to validators  
as it's completely redundant. See http://trac.agavi.org/ticket/767 for  
details.

Greetings,

David

_______________________________________________
Agavi Dev Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/dev

Reply via email to