The overview of my goal is to replace 1 2 3 4 with prev next. I
can't see how it can be done through subclassing, so I'm rolling my own
Panel, similar to PagingNavigator (but with a new template).
I'm trying to get AJAX pagination working, and I have--without custom stuff.
If I use
INFO:
INFO: Initiating Ajax GET request on
/app?wicket:interface=:1:topDogsBlock:pager:next::IBehaviorListenerwicket:behaviorId=0random=0.28339447129400336
INFO: Invoking pre-call handler(s)...
ERROR: Received Ajax response with code: 500
INFO: Invoking post-call handler(s)...
INFO: Invoking
That is an internal error. Which means that you got an exception. We
need to see the exception (from your server logs).
-Matej
On 5/15/07, Tremelune [EMAIL PROTECTED] wrote:
INFO:
INFO: Initiating Ajax GET request on
No exceptions thrown, at least nothing reported by my app.
AjaxPagingNavigator doesn't get hit at all. What would come before that? I
don't think it's in any of my code before it gets to AjaxPagingNavigator.
The question remains, how can identical code be failing in one case and not
the other
On 5/15/07, Tremelune [EMAIL PROTECTED] wrote:
No exceptions thrown, at least nothing reported by my app.
something cause error code 500, so there must be an exception somewhere in
the logs.
AjaxPagingNavigator doesn't get hit at all. What would come before that?
before that wicket has
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
Did you think of copying the templates (ie the html files) that are
associated with the navigator components?
I did succeed in extending the navigator, and also made it work with Ajax. I
must say, it was not an easy thing to do.
Regards,
Erik.
Tremelune wrote:
Line for line,
it's the
So I have to register my AJAX stuff with a particular behavior? That is what
I suspected, but I'm having trouble figuring out where/how that takes place.
The examples don't bother with this since they're using the default classes.
Something googlable besides wicket ajax behavior would point me in
class mynav extends ajaxpagingnavigator {
newnavigation(...) {
// hide the 1 2 3 4
return super.newnavigation(..).setvisible(false);
}
newpagingnavigationlink(..) {
//hide first last
return super.newpagingnavigationlink(..).setvisible(False);
}
}
thats all you want right? you will be left
or you can simply roll your own class since building a navigator should
be pretty trivial.
-igor
On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
class mynav extends ajaxpagingnavigator {
newnavigation(...) {
// hide the 1 2 3 4
return super.newnavigation(..).setvisible(false);
}
10 matches
Mail list logo
