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 2005/12/09 15:52:08 UTC

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

     [ http://issues.apache.org/jira/browse/FOR-701?page=all ]

Ross Gardler updated FOR-701:
-----------------------------

    Fix Version:     (was: 0.8-dev)
       Priority: Minor  (was: Critical)

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

> 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


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

Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> This was referring to the message that is shown in the browser.
> Is that improved now?

No, that is covered in http://issues.apache.org/jira/browse/FOR-701

Note that this is blocked by a Cocoon issue: 
http://issues.apache.org/jira/browse/COCOON-1542

Ross


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

Posted by David Crossley <cr...@apache.org>.
This was referring to the message that is shown in the browser.
Is that improved now?

-David

Ross Gardler (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/FOR-701?page=all ]
> 
> Ross Gardler updated FOR-701:
> -----------------------------
> 
>     Fix Version:     (was: 0.8-dev)
>        Priority: Minor  (was: Critical)
> 
> Reducing priority and moving to an unreleased version. Logs now give meaningful information.
> 
> > 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