abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Primmer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ABDERA-182) Add accessor methods for Route.requirements and defaultValues
Date Tue, 01 Jul 2008 08:23:45 GMT

    [ https://issues.apache.org/jira/browse/ABDERA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609488#action_12609488

David Primmer commented on ABDERA-182:

I've looked at 139's requirements patch, the only issue i have with it is it doesn't let me
do what i want with the requirements. It's a way to filter on your variables that are matched
to path segments. (and it appears this is how it works in Python routes). However, I want
to set a requirement on a url param being present, which is after the ? and so not part of
the URI in the case of the patch in 139. This is why I put in generic accessor methods. Then
I use the requirements during the resolve.

> Add accessor methods for Route.requirements and defaultValues
> -------------------------------------------------------------
>                 Key: ABDERA-182
>                 URL: https://issues.apache.org/jira/browse/ABDERA-182
>             Project: Abdera
>          Issue Type: Improvement
>            Reporter: David Primmer
>         Attachments: abdera-182_Route_accessor_methods.patch
> I'd like to start using requirements but the values are not available on the Route object.
This is a start to adding support for actually using the requirements field in some way in
the RouteManager's resolve method (or maybe in Route.match).

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

View raw message