PageParameters in 1.5.3 vs 1.5.4

["Lawrence, Sean" <Se...@ManTech.com>]

Hi,

I'm noticing a difference in the way search parameters are handled in 1.5.4 vs 1.5.3 after upgrading wicket. Basically, identical parameters are eliminated. See example below

Passing the identical list of search parameters to our SearchResultsPage:

URL with 1.5.3:

https://localhost/app/wicket/bookmarkable/pages.SearchResultsPage?41&params&qt1=QUERY&mf1=dDocTitle&pr=%3Csubstring%3E&op1=%3COR%3E&qt1=QUERY&mf1=name&pr=%3Csubstring%3E&op1=%3COR%3E&qt1=QUERY&mf1=nameCO&pr=%3Csubstring%3E&op1=%3COR%3E&qt1=QUERY&mf1=nameCS&pr=%3Csubstring%3E&op1=%3COR%3E&qt1=QUERY&mf1=ddd&pr=%3Csubstring%3E&op1=%3COR%3E&qt1=QUERY&mf1=abNumber&pr=%3Csubstring%3E&op1=%3COR%3E&sortField=dCreateDate&sortOrder=desc&sortField=dDocTitle&sortOrder=asc&as=false&qs=true

URL with 1.5.4:

https://localhost/app/wicket/bookmarkable/pages.SearchResultsPage?30&params&qt1=QUERY&mf1=dDocTitle&mf1=name&mf1=nameCO&mf1=nameCS&mf1=ddd&mf1=abNumber&pr=%3Csubstring%3E&op1=%3COR%3E&sortField=dCreateDate&sortField=dDocTitle&sortOrder=desc&sortOrder=asc&as=false&qs=true

Noticed how the identical op1=<OR>, pr=<substring>, and qt=QUERY params were all reduced to one entry in 1.5.4.

Because we are dependent on 1.5.3's behavior for our searches the 1.5.4 behavior is breaking things, as well as eliminating the ability to keep rows synced across columns when parameters might be related.

Questions:

(1) Will the way 1.5.4 is handling identical search parameters be the desired behavior going forward with Wicket and

(2) if this is the desired behavior is there a better way to handle our searches that involve syncing across columns/arrays like this (with variable rows) ?

Thanks,

Sean Lawrence