Missing locationmap entry gives poor error

• Key: FOR-701
• Type: Bug
• Status: Reopened
• Priority: Minor
• Assignee: Unassigned
• Reporter: Ross Gardler
• Component/s: Locationmap

Description

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.

Comments

[Tim Williams]

Indicated "locationmap" component

[Ross Gardler]

Reducing priority and moving to an unreleased version. Logs now give meaningful information.

[Ross Gardler]

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.

[Ross Gardler]

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

[Ross Gardler]

Needs improvement, but at least the error now says the problem is in the locationmap!

[Ross Gardler]

Reopened as the fix prevented broken-links.xml from being generated.

the fix is currently commented out in the root sitemap.