Matej,
I'm stuck with a similar problem with Ajax replace and back button which I
initially mentioned here:
http://www.nabble.com/Ajax-component-replaceWith-and-browser-back-button-problems-tf3479357.html#a9710492
That problem is still there in todays snapshot. Recently I was trying to
get to
Hi,
at actually looks like the bug. What you can try to do is to enable
versioning on the link. What's the URL the link generates? Does it
contain IUnversionedBehaviorListener? If it does you should have the
AbstractDefaultAjaxBehavior.getCallbackScript called with first
parameter = true.
-Matej
Try overriding isVersioned (of you page, though it works on components
as well) and let it return false.
Eelco
On 4/27/07, jamieballing [EMAIL PROTECTED] wrote:
We are experiencing a problem in our application because we are doing
something out of the ordinary.
We have an applet on our
This is wrong. Even if page version increments, the ajax links should
be valid. There was a bug in wicket 1.3 where the wicket still allowed
you to do unversioned ajax requests, but that's should be gone
already. Can you please test it with most recent 1.3?
-Matej
On 4/27/07, jamieballing [EMAIL
We are currently using the incubating-beta1 release. I was stepping through
the source in a debugger and I'm not sure older versions of the page are
preserved in the cache (at least when update by an ajax request). I did a
simple test:
* I went to a versioned page
* clicked an ajax control which
We are experiencing a problem in our application because we are doing
something out of the ordinary.
We have an applet on our page which makes a wicket request on behalf of the
page. The request is a form submit which causes a file upload, but it
doesn't affect the state of the page. When wicket
