[
https://issues.apache.org/jira/browse/TAP5-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836085#action_12836085
]
Leonard Lu commented on TAP5-1018:
----------------------------------
This issue could be handled by having the RootPathDispatcher send a redirect
rather than handling the request itself.
For other searchers, a lovely graphic with the Tapestry5 request processing
pipelines is available at
http://tapestry.formos.com/nightly/tapestry5/images/tapestry_request_processing_800.png,
which makes it clear that the current intended behavior is for RootPath to
completely bypass the Asset, ComponentEvent and PageRender Dispatchers.
> Request to Application Root path ignores ComponentRequestFilter's
> -----------------------------------------------------------------
>
> Key: TAP5-1018
> URL: https://issues.apache.org/jira/browse/TAP5-1018
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Everton Agner Ramos
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
