Tapestry
  1. Tapestry
  2. TAPESTRY-2042

Make it possible to merge action requests with rendering, as with Tapestry 4

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.8
    • Component/s: tapestry-core
    • Labels:
      None

      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.

        Activity

        Hide
        Massimo Lusetti added a comment -

        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

        Show
        Massimo Lusetti added a comment - 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

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development