Tapestry 5
  1. Tapestry 5
  2. TAP5-74

Provide a way that a component sub-class can merge its template with that of its container

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.15
    • Fix Version/s: 5.1.0.1
    • Component/s: None
    • Labels:
      None

      Description

      This is an idea I've picked up from Wicket; which has a special element, similar to Tapestry t:body, but used to indicate where the child component's template should go. In Wicket, pages are often given a common L&F not by the use of a common component, but by extending a common base class, and mixing the base class' template with the sub-class.

        Activity

        No work has yet been logged on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development