[ http://issues.apache.org/jira/browse/FOR-701?page=comments#action_12359950 ]
Ross Gardler commented on FOR-701: ---------------------------------- Now that Forest throws an exception when the final location returned is a null we can (probably) trap this error in our sitemap and provide a more meaningful error message. It is unlikely that the Cocoon issue will be resolved as it has wider implications and side-effects. > Missing locationmap entry gives poor error > ------------------------------------------ > > Key: FOR-701 > URL: http://issues.apache.org/jira/browse/FOR-701 > Project: Forrest > 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. - 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
