forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Williams (JIRA)" <>
Subject [jira] Commented: (FOR-705) Target of LocationMap rewriteDemo causes build failure when target not available
Date Thu, 22 Jun 2006 21:16:30 GMT
    [ ] 

Tim Williams commented on FOR-705:

I don't have time to look into the best way to fix this right now - maybe this comment will
spark some thoughts.  

I'm pretty sure this is happening because the match for the rewrite is in the project-level
locationmap and the project-level locationmap is being mounted within a selector.  So when
results come back from it, they are coming back through the SelectNode, which, obviously,
uses the selector to determine existence and only returns successful ones e.g.:

              if (,om,parameters)) {
                  debug("Selected: " + location);
                  return location;
              } else {
                  debug("Not selected: " + location);

When the match is a bum URL, even though location is string is properly retrieved, it will
never make it all the way back up because of the selector logic. 

Since I'm having to work with very small fragments of time when I can get them, I'm going
to rely on comments like this to remind me where I'm at when I get back to it. 

> Target of LocationMap rewriteDemo causes build failure when target not available
> --------------------------------------------------------------------------------
>          Key: FOR-705
>          URL:
>      Project: Forrest
>         Type: Bug

>   Components: Locationmap
>     Versions: 0.8-dev
>     Reporter: Gavin
>      Fix For: 0.8-dev

> Build fails when given target URL of rewriteDemo is not available (site down, no longer
exists, incorrect URL typing etc).
> For various reasons given in [1] and [2] this default feature should remain but alternative
options should be made available. Possible solutions given in [3]
> [1]
> [2]
> [3]

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message