I did copy the template into my source tree (as with all other templates),
but it does not appear to be used. I changed the IDs to be bad values and it
didn't explode. It just seems to use whichever one is used by
PagingNavigator (PagingNavigator.html in the jar).
Most of this trial/tribulation stems from the fact that PagingNavigator has
the following code in the constructor:
add(newPagingNavigationLink("first", pageable, 0));
add(newPagingNavigationIncrementLink("prev", pageable, -1));
add(newPagingNavigationIncrementLink("next", pageable, 1));
add(newPagingNavigationLink("last", pageable, -1));
There is simply no way to remove the "first" and "last" elements from this
componant. As such, the app explodes if the template is missing these two as
well.
I may just pull this stuff into an overridable method and see what
happens...I don't really like customizing third party software--makes it
more difficult to maintain. Maybe I can override newPagingNavigationLink()
to do nothing, but...Just seems like a bit of a hack.
--
View this message in context:
http://www.nabble.com/AjaxPagingNavigator-doesn%27t-work-as-%22custom%22-class-tf3760248.html#a10630281
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
