[jira] Commented: (TAPESTRY-2042) Make it possible to merge action requests with rendering, as with Tapestry 4

["Massimo Lusetti (JIRA)" <de...@tapestry.apache.org>]

    [ https://issues.apache.org/jira/browse/TAPESTRY-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558559#action_12558559 ] 

Massimo Lusetti commented on TAPESTRY-2042:
-------------------------------------------

Yes please don't turn it back.

New behaviour turned out very nice and clean and for stateless applications/services is still possibile to leverage the activation context mechanism

> Make it possible to merge action requests with rendering, as with Tapestry 4
> ----------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2042
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2042
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>            Reporter: Howard M. Lewis Ship
>             Fix For: 5.0.8
>
>
> For some applications, it would be nice if Tapestry would support Tapestry 4's request cycle: action requests immediately render a markup (HTML) response rather than send a redirect.
> This would make it easier to support stateless applications.
> It would still be possible to get redirect-after-action behavior, by returning an Link instance from an event handler method.
> I strongly oppose making this the default, since I think the user experience (i.e., bookmarkable URLs, non-repeating of form submissions, etc.) is significantly better using the default T5 approach.
> This would be an application-wide configuraton value.

-- 
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org