Tapestry 5
  1. Tapestry 5
  2. TAP5-1018

Request to Application Root path ignores ComponentRequestFilter's

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2, 5.1.0.5
    • Fix Version/s: 5.2.0, 5.1.0.8
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Example:

      I've made a ComponentRequestFilter to handle Locale issues... And if I request [ /t5app/Start ] page, my Filter code is executed. But, if I request the Application Root path [ /t5app or /t5app/ ] it ignores the Filter and avoids it.

      -------------

      Following [Thiago H. de Paula Figueiredo] comment:

      I've looked at the sources and I've found that RootPathDispatcher, the dispatcher that handles the root URL, doesn't invoke the ComponentEventHandler, which is the pipeline that invokes the ComponentEventFilter's. This is a bug, so please file a JIRA about it.

        Activity

          People

          • Assignee:
            Ulrich Stärk
            Reporter:
            Everton Agner Ramos
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development