[ http://issues.apache.org/jira/browse/FOR-732?page=comments#action_12357755 ]
Tim Williams commented on FOR-732: ---------------------------------- I'm pretty sure it is a result of caching. We're caching the null results too right now, this is important because of having an exists selector. I think null's shouldn't be cached at the locationmap module level and should probably be done at a lower level so that it can be done more granularly. --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
