[TAPESTRY-2042] Make it possible to merge action requests with rendering, as with Tapestry 4

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.0.8
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 13/Jan/08 23:14
• Updated: 14/Jan/08 23:37
• Resolved: 14/Jan/08 23:37

Description

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.