[
https://issues.apache.org/jira/browse/TAP5-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-515.
-------------------------------------
Resolution: Won't Fix
The fact that it passes through Tapestry and to the servlet container is by
design. Strangely, other users want to go the other way, and have malformed
URLs (that look like component events but aren't really) be passed through as
normal 404s. There's not pleasing everyone.
> HTTP 404 response if page-class couldn't be found -> improvement: exception
> page explaining the cause
> -----------------------------------------------------------------------------------------------------
>
> Key: TAP5-515
> URL: https://issues.apache.org/jira/browse/TAP5-515
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.0
> Reporter: manuel aldana
> Priority: Minor
>
> If page class cannot be found (corresponding to template), you get a 404
> response.
> It would be nicer to wrap this error and report the cause to this nice
> tapestry error-reporting page and suggest the fix (e.g. by wrapping the
> ClassNotFoundException to a meaningful message).
> This tapestry user-error is not so unlikely:
> -page class accidently not put to xxxx.pages package
> -wrong tapestry app root-package configuration in web.xml
> (tapestry.app-package param)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
