beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie O'Neil (JIRA)" <>
Subject [jira] Resolved: (BEEHIVE-1042) MutableURI class should preserve the order of the query string parameters.
Date Sat, 14 Jan 2006 18:51:34 GMT
     [ ]
Eddie O'Neil resolved BEEHIVE-1042:

    Resolution: Fixed

Fixed with SVN 369073.  MutableURI now maintains order of parameters by their order parsed
from a query string or in order of addition.  

> MutableURI class should preserve the order of the query string parameters.
> --------------------------------------------------------------------------
>          Key: BEEHIVE-1042
>          URL:
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Carlin Rogers
>     Assignee: Eddie O'Neil
>     Priority: Minor
>      Fix For: 1.0.1

> name3=value3a&name2=value2&name1=value1&name3=value3b
> becomes...
> name3=value3a&name3=value3b&name2=value2&name1=value1
> Need a data structure change in MutableURI to solve the problem.
> We do in fact handle our parameters in a LinkedHashMap for order, where the parameter
name are the key. 
> However, since a parameter name may have more than one value assigned to the name, the
associated value is an ArrayList. Then when we write the query string, we go through the ordered
set of names and write all of the values for each name. Therefor, all the values of a given
name are grouped together.
> In this case above, grouping the last "name3" value to the front to follow the first
occurrence of a "name3" value, followed by name2 and name 1, is a subtle change to the overall
> It shouldn't be too hard/risky to change the data structure so that we just keep all
the values in the original order.

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