You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Parson (JIRA)" <ji...@apache.org> on 2012/12/03 17:45:58 UTC

[jira] [Created] (WICKET-4905) PagingNavigation: possible to call setStartIndex() earlier than onBeforeRender?

Peter Parson created WICKET-4905:
------------------------------------

             Summary: PagingNavigation: possible to call setStartIndex() earlier than onBeforeRender?
                 Key: WICKET-4905
                 URL: https://issues.apache.org/jira/browse/WICKET-4905
             Project: Wicket
          Issue Type: Improvement
          Components: wicket
    Affects Versions: 6.2.0
            Reporter: Peter Parson
            Priority: Minor


PagingNavigator has two actions in its onBeforeRender implementation:

setDefaultModel(new Model<Integer>((int)Math.max(Integer.MAX_VALUE, pageable.getPageCount())));
setStartIndex();

Building my own PagingNavigation extending PagingNavigation, not being able to retrieve the start index before onBeforeRender, forces me to put a lot of logical code into my own onBeforeRender implementation.
So there's a valid workaround, but I'd expect this to work from onConfigure also, maybe even from onInitialize.

As far as I can see it should be possible to call the two methods earlier than onBeforeRender, however I might be missing the "big picture" and oversee some side effects this could cause.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira