[ http://issues.apache.org/jira/browse/TAPESTRY-670?page=comments#action_12427663 ] Andreas Andreou commented on TAPESTRY-670: ------------------------------------------
AFAICT, resolve(IRequestCycle cycle, String prefixedName) of PageSpecificationResolverImpl is the only place where such an exception is thrown. That methods already knows the page in question (_simpleName) and builds an error message using it. So, adding an additional constructor PageNotFoundException(String page, String message) and providing a getter is all it takes to fix this. I believe it's worth it, anyone against this? > PageNotFoundException should include the requested page name as a property > -------------------------------------------------------------------------- > > Key: TAPESTRY-670 > URL: http://issues.apache.org/jira/browse/TAPESTRY-670 > Project: Tapestry > Issue Type: Improvement > Components: Framework > Affects Versions: 4.0 > Reporter: Leonardo Quijano Vincenzi > Assigned To: Andreas Andreou > Priority: Minor > > I think the summary says it all. It's useful for custom "page not found" > pages to extract the requested page name from the PageNotFoundException and > display customized messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
