Running direct with the source code, it throws an Exception in
AjaxPagingNavigationBehavior:
protected void onEvent(AjaxRequestTarget target)
{
// handle the event
owner.onClick(target);
// find the PagingNavigator parent of this link
AjaxPagingNavigator navigator =
(AjaxPagingNavigator)((Component)owner)
.findParent(AjaxPagingNavigator.class);
if (navigator == null)
{
throw new WicketRuntimeException(
"Unable to find AjaxPagingNavigator
component in hierarchy starting
from "
+ owner);
}
// tell the PagingNavigator to update the IPageable
navigator.onAjaxEvent(target);
}
navigator is null at this point, and the WicketRuntimeException is thrown.
Should I be explicitly setting the parent or something?
AjaxPagingNavigationBehavior seems tied to AjaxPagingNavigator, which I do
not intend to use.
Dunno why my app is swallowing this Exception, but that's my own problem.
--
View this message in context:
http://www.nabble.com/AjaxPagingNavigator-doesn%27t-work-as-%22custom%22-class-tf3760248.html#a10629869
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
