[
https://issues.apache.org/jira/browse/TAP5-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763937#action_12763937
]
Christophe Cordenier commented on TAP5-879:
-------------------------------------------
I am 'humbly' trying to implement a patch for this but i 'need to pick your
brain' (not sure of this expression, i assume my dictionnary is right)
To let the request pass through TapestryFilter seems to be the best solution
(let the servlet container handle 404), actually as far as i know, to achieve i
have to return false in the PageRenderDispatcher. My problem is how to verify
if the target page implements the activation method since the only way i have
found to achieve this is to check the return value of triggerEventContext ?
Another way (that i don't really like) is to send an error in the
PageRenderRequestHandler after page activation ?
Have you any other ideas i can explore ?
> 404 is never raised automatically if the application has an index page.
> -----------------------------------------------------------------------
>
> Key: TAP5-879
> URL: https://issues.apache.org/jira/browse/TAP5-879
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Christophe Cordenier
>
> The default behavior of PageRenderDispatcher when a user access to a URL like
> 'http://localhost/demo/blah' (where 'demo' is the application context and
> 'blah' is a page that does not exist) is to translate to
> 'http://localhost/demo/index/blah' if an index page exists even if it has no
> activation method.
> It could be a better solution to check if a the index page has an activation
> method with the corresponding parameter number and type, and automatically
> raise a http 404 if not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
