Hi, I din't find were javadoc says that AjaxPagingNavigationIncrementLink can to be used as standalone component
*AjaxPagingNavigationIncrementLink *javadoc: An incremental Ajaxian link to a page of a PageableListView. Assuming your list view navigation looks like [first / << / <] 1 | 2 | 3 [> / >> /last] and "<" meaning the previous and "<<" goto the "current page - 5", than it is this kind of incremental page links which can easily be created. This link will update the pageable and itself or the navigator the link is part of using Ajax techniques, or perform a full refresh when ajax is not available. nor were the navigator is just optional to AjaxPagingNavigationBehavior *AjaxPagingNavigationBehavior * only contructor javadoc: Attaches the navigation behavior to the owner link and drives the pageable component. The behavior is attached to the markup event. Parameters: *owner* the owner ajax link *pageable* the pageable to update * event* the javascript event to bind to (e.g. onclick) On Thu, Sep 10, 2009 at 5:11 AM, Andrej Thiele <[email protected]>wrote: > Hi, > I tried to use the AjaxPagingNavigationIncrementLink as standalone > component. As javadoc describes this should be possible like using the > PagingNavigationIncrementLink. But if I click on this link an exception is > the result. > > After diving into the code I have seen that the > AjaxPagingNavigationBehavior searches for a AjaxPagingNavigator component > which is not present in my code. The javadoc to this behavior says that the > navigator is just optional. > > Is this a problem in the wicket code or is there another possibility to use > an incremental link together with ajax? > > Best regards, > > Andrej > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
