Add configuration to defeat the Tapestry action/render request split, allowing
action requests to render responses directly
---------------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-2011
URL: https://issues.apache.org/jira/browse/TAPESTRY-2011
Project: Tapestry
Issue Type: New Feature
Components: tapestry-core
Reporter: Howard M. Lewis Ship
I think T5's basic action/render split is a Good Thing that will make End Users
Happy. But it is controversial and there's been some pushback (from some of my
clients) that they want a traditional approach.
I see this as a configuration value, a symbol,
tapestry.render-action-response-directly perhaps, that can be set to true (but
default to false) that would take effect application-wide.
Basically, all that needs to change is for the the handling of String and Class
return values from event handler method to render the response in-request,
rather than send a redirect.
Event handler methods can today, and will in the future, return a Link instance
to force a redirect to the Link. This will allow, much as in T4, specific
forms to implement a redirect-after-post, even if the rest of the app is in the
"traditional" mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
