if wicket is resolving BookmarkablePageRequestTarget then it thinks it is being sent a bookmarkable url. check which url is being sent by the ajax request.
-igor On Fri, Oct 1, 2010 at 7:40 AM, A. Zwaan <a.zw...@finan.nl> wrote: > Hello all, > > I seem to have a problem with BookmarkablePage and it triggering a full page > rebuild after an ajax call, while the Ajax call was only meant to update > several fields. > > The situation is as follows; Our application has a grid with input fields, we > use an Ajax behaviour on this grid to process input in these fields and > update other fields when values have changed based on the input. Only the > values are sent over and updated, not the wicket panels the inputs were on. > Now after this Ajax update request has finished, for some reason the page > gets rebuild completely (constructor is called through newInstance()). > > This didn't happen before (we are doing a large refactoring of the app), and > none of the recent changes looks like they could have caused this problem, > though ofcourse I might have missed something. I tried to trace the problem, > but it goes deep into wicket and that it has something to do with the > BookmarkablePageRequestTarget is as far as I got. > > Anyone have any idea on what could cause this problem and how to fix it? > > Thanks in advance for your time. > > > Regards, > Arjan Zwaan. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
