Tapestry
  1. Tapestry
  2. TAPESTRY-1464

Cannot Subclass TapestryFilter to add custom init() and destroy() logic

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.5
    • Fix Version/s: 5.0.5
    • Component/s: Core Components
    • Labels:
      None
    • Environment:
      Any.

      Description

      Please either un-finalize the init() method (and optionally the destroy() method) OR within it, make a call to a secondary sub-init() method that your class can do-nothing, but that can then be overridden but groups (like us) needing to do secondary initializations during the start up. THANKS!

        Activity

        No work has yet been logged on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development