[jira] Updated: (ABDERA-111) Route matching shouldn't span segment boundaries

["Jim Ancona (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ABDERA-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Ancona updated ABDERA-111:
------------------------------

    Attachment: Route.patch

Here's a unit test and patch. The patch replaces the match and parse code with regexs.

> Route matching shouldn't span segment boundaries
> ------------------------------------------------
>
>                 Key: ABDERA-111
>                 URL: https://issues.apache.org/jira/browse/ABDERA-111
>             Project: Abdera
>          Issue Type: Bug
>            Reporter: Jim Ancona
>             Fix For: 0.4.0
>
>         Attachments: Route.patch
>
>
> I have run into some problems with my Routes matching unexpectedly. 
> The current algorithm attempts to match the non-variable parts of the pattern, setting the variable to whatever is in between.
> So the pattern "/base/:collection/" matches both "/base/test/" and "/base/test/123/". In the second case, the value of the collection variable is "test/123". In my opinion, not allowing matches to span URI segments would be less prone to unintuitive results.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.