Thanks for the reply.
We had to develop our own self-updating behavior since wicket does not
provide any means for enabling/disabling auto-update per user request.
Igor Vaynberg wrote:
its probably because your ajax urls are creating new versions of pages
- and when you submit the form it
Hi all,
I have a submit button that sets response page to some other page after
form is submitted (I override Form.delegateSubmit).
In addition there is an AJAX link in that page that refreshes some
components in the page every 5 seconds.
Since we cannot disable AjaxSelfUpdatingTimerBehavior we
its probably because your ajax urls are creating new versions of pages - and when you submit the form it unrolls the page version. why cant you use the self updating behavior? if you dont - which is fine - you have to construct the url exactly like it does - those urls do not construct/nor
