Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-2025

Centralize page/component class resolution logic

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 5.0, 5.0.7, 5.0.8
    • Fix Version/s: None
    • Component/s: Framework, tapestry-core
    • Labels:
      None

      Description

      The PageRenderDispatcher and ComponentActionDispatcher each have to decipher the component or page being requested. The resolution of the associated class in each case is essentially the same. I'm working (again) on a transparent access control system that must do the same thing, so I've basically copy/pasted this logic. It would seem to make sense (and also be convenient for me) to centralize this logic somewhere - probably as a static method. This would also insulate code like mine against breakage.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: