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] Updated: (ABDERA-95) DefaultProvider doesn't properly handle parameters in base routes
Date Wed, 30 Jan 2008 19:55:37 GMT

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

Jim Ancona updated ABDERA-95:

    Attachment: RouteManager_workaround.patch

Further analysis show that the problem occurs when calling AbstractCollectionAdapter.getHref(RequestContext
request), which calls request.urlFor("feed", hrefParams). Because hrefParams doesn't contain
the parameters for the base part of the URI, the wrong href is returned.

This patch is a workaround. I have RouteManager add the missing parameters to the HashMap
before building the context. This only works when the params are in a HashMap (which they
are in this case). I can't figure out how to handle the other cases properly.

Perhaps this will help you find a better solution.

> DefaultProvider doesn't properly handle parameters in base routes
> -----------------------------------------------------------------
>                 Key: ABDERA-95
>                 URL: https://issues.apache.org/jira/browse/ABDERA-95
>             Project: Abdera
>          Issue Type: Bug
>            Reporter: Jim Ancona
>         Attachments: CustomerAdapterTest.patch, RouteManager_workaround.patch
> I spent some time trying to debug this last night, but didn't find the solution. I will
attach a unit test patch that reproduces the problem.

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

View raw message