[jira] Closed: (TAPESTRY-2237) Grid should make its "currentPage" value available to containing components

["Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>]

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

Howard M. Lewis Ship closed TAPESTRY-2237.
------------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: unspecified)
                   5.0.11
         Assignee: Howard M. Lewis Ship

> Grid should make its "currentPage" value available to containing components
> ---------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2237
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2237
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Core Components
>    Affects Versions: 5.0.11
>         Environment: any
>            Reporter: Robert Zeigler
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.0.11
>
>         Attachments: grid_currentpage_accessors.patch
>
>
> With the introduction of the @GenerateAccessor annotation, tapestry's core components were stripped of their "getters" and "setters".  But Grid's currentPage property should be accessible via java code, and not 100% internal to the component. There are many cases where a container may want or need to change the current page, outside of the standard "pager" links.  Without the accessors, this is non-trivial (ie requires reflection).  

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org