Tapestry
  1. Tapestry
  2. TAPESTRY-440

Public API for rendering pages inside a page/component

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 4.1
    • Component/s: Framework
    • Labels:
      None

      Description

      Many people seem to be using Tapestry to render emails inside the applications.
      With tapestry 3.0, it was possible to store the get the value of the current form attribute, create a writer, render a page inside the current RequestCycle (for generating the email) and finally restore the form attribute.
      With all the changes in Tapestry 4, this process is not straightforward to translate, and also I think this process should be hidden inside the framework.

      Suggestion: add a method inside the IRequestCycle (or another Tapestry service) to render a page to a writer.

        Activity

        Hide
        Jesse Kuhnert added a comment -

        The management of written content can now be controlled by providing your own implementation of the hivemind ResponseBuilder service configuration point. (to be documented soon)

        Show
        Jesse Kuhnert added a comment - The management of written content can now be controlled by providing your own implementation of the hivemind ResponseBuilder service configuration point. (to be documented soon)

          People

          • Assignee:
            Unassigned
            Reporter:
            Henri Dupre
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development