You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2007/03/22 02:05:32 UTC

[jira] Commented: (FOR-701) Missing locationmap entry gives poor error

    [ https://issues.apache.org/jira/browse/FOR-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482975 ] 

Ross Gardler commented on FOR-701:
----------------------------------

I've added some basic error handling for the ResourceNotFound case we get when the locationmap fails to resolve a request.

It's still not great but it is a small improvement and, more importantly, paves the way for better error reporting using exception-to-html.xsl

> Missing locationmap entry gives poor error
> ------------------------------------------
>
>                 Key: FOR-701
>                 URL: https://issues.apache.org/jira/browse/FOR-701
>             Project: Forrest
>          Issue Type: Bug
>          Components: Locationmap
>            Reporter: Ross Gardler
>            Priority: Minor
>
> If there is no locationmap entry for a resource we get a "resource not found" error. This is fine if it is the actual source file that is missing. However, now that we are using the LM to find other intermediate resources, such as stylesheets etc. it can be misleading.
> We need to throw a meaningful error when when a resource cannot be found.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.