forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Williams (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-732) Changing the locationmap after a resource not found error has no effect
Date Tue, 06 Dec 2005 06:00:08 GMT
    [ http://issues.apache.org/jira/browse/FOR-732?page=comments#action_12359380 ] 

Tim Williams commented on FOR-732:
----------------------------------

When it's detected that the locationmap is not valid, the cache needs to be flushed or the
reload of the locationmap will have no effect.  This is easy enough for the core locationmap
but as a result of having caching at the module level, there's no way to flush the cache based
on a mounted locationmap becoming invalid. 

*These are more or less notes so that I have something to make me remember where I was at
with this.
--tim

> Changing the locationmap after a resource not found error has no effect
> -----------------------------------------------------------------------
>
>          Key: FOR-732
>          URL: http://issues.apache.org/jira/browse/FOR-732
>      Project: Forrest
>         Type: Bug
>   Components: Locationmap
>     Versions: 0.8-dev
>     Reporter: Ross Gardler

>
> If a resource is requested and is not found, then a change is made to the locationmap
to ensure the resource  is found, Forrest requires a reboot for the change to be noted.
> This may be as a result of in-progress work on FOR-711 or may be unrelated.

-- 
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


Mime
View raw message