[jira] Resolved: (BEEHIVE-171) Ability to add parameters to the pager query

["Eddie O'Neil (JIRA)" <be...@incubator.apache.org>]

     [ http://issues.apache.org/jira/browse/BEEHIVE-171?page=history ]
     
Eddie O'Neil resolved BEEHIVE-171:
----------------------------------

     Resolution: Fixed
    Fix Version: V1Beta

The pager URLs now maintain the existing query parameters.  Note, this doesn't allow you to *add* new query parameters to the URL, but it does 'carry along' the query parameters from the previous request.

> Ability to add parameters to the pager query
> --------------------------------------------
>
>          Key: BEEHIVE-171
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-171
>      Project: Beehive
>         Type: Improvement
>   Components: NetUI
>     Versions: V1Alpha
>  Environment: Beehive Alpha 1.0 snapshot 
>     Reporter: Adrian Grealish
>     Assignee: Eddie O'Neil
>      Fix For: V1Beta

>
> What I need is to be able to add parameters to the pager query strings.
>  
> I have a parent child relationship where the parent record has many
> children records. I have a data grid that displays all the child records given the parent record's primary key. 
> The page flow method, 'viewGrid', that displays the data grid checks for 
> the request parameter 'parentId' and then does a select * from child_table where
> foreign_key_to_parent_table = <parentId>. When I click on the 'next'
> link of the data grid the same page flow method, 'viewGrid', is called
> again but this time without the URL encoded parameter causing the SQL
> query to fail.
> As a test I hard coded the parameter into the pageAction attribute (pageAction="viewGrid?testSuiteRunId=1") but his results in the mal-formed URL "...viewGrid.do?testSuiteRunId=1?netui_page=TestCaseResults~2" which
> does not work.
> If I manually type the correct URL (".../viewGrid.do?netui_page=TestCaseResults~2&testSuiteRunId=1") into a browser it works.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira