abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Ancona (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (ABDERA-162) RouteManager.urlFor shouldn't read params from request
Date Mon, 27 Oct 2008 19:43:44 GMT

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

Jim Ancona reopened ABDERA-162:

Could someone explain why the behavior being removed here (RouteManager.urlFor() using request
parameters to expand a URL) was a bug? The description of this issue doesn't help much. 

Our use case is that we have a provider with a base URL that is itself parameterized, e.g.
"/customers/:customerName/". In order for the adapter lookup in DefaultWorkspaceManager to
work properly, the :customerName parameter has to be expanded with the parameter from the

I just spent a couple days tracking down a problem that showed up when moving our code to
0.5.0. It turned out to be caused by this change. 



> RouteManager.urlFor shouldn't read params from request
> ------------------------------------------------------
>                 Key: ABDERA-162
>                 URL: https://issues.apache.org/jira/browse/ABDERA-162
>             Project: Abdera
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: David Calavera
>             Fix For: 0.5.0
>         Attachments: urlFor.patch

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

View raw message