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 the root of this and created a quickstart. But then I ran into what
looks like another related problem which I raised here:
https://issues.apache.org/jira/browse/WICKET-491
Please help!
Thanks,
Peter.
On 4/30/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
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
On 4/30/07, jamieballing <[EMAIL PROTECTED]> wrote:
>
> 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 updates that page
> * hit my browser back button (which didn't actually go to the server but
> reloaded the locally cached page)
> * clicked on another ajax control on the page
> At this point I got a page expired message.
>
> This raises a couple questions:
> 1) This doesn't sound like the bug you are describing... Is the behavior
we
> are observing correct behavior?
> 2) Do we need to do anything to enable or set the size of the page
cache?
> 3) Is there a more recent version we should be using than the
> incubating-beta1 snapshot?
>
> Many Thanks,
> Jamie
>
>
> Matej Knopp-2 wrote:
> >
> > 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 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 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 1.3 processes the
> >> request
> >> and calls getResponsePage() it identifies the response as an instance
of
> >> PageRequestTarget which causes the last version in the cache to
> >> increment.
> >>
> >> The applet doesn't do anything with the response from wicket, so the
> >> existing wicket urls on the page all still refer to the old page
version.
> >> Therefore, when you click anything (e.g. ajax links) we get a page
> >> expired
> >> because the versioning is out of synch.
> >>
> >> How would you recommend we approach this problem? Is there someway to
> >> tell
> >> wicket in the request not to increment the last page version or tell
it
> >> that
> >> we are using a different target type than PageRequestTarget?
> >>
> >> Thanks,
> >> Jamie
> >> --
> >> View this message in context:
> >>
http://www.nabble.com/Way-to-prevent-page-versioning-for-a-request-in-1.3--tf3658645.html#a10222425
> >> 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
> >> Wicket-user@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/wicket-user
> >>
> >
> >
-------------------------------------------------------------------------
> > 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
> > Wicket-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wicket-user
> >
> >
>
> --
> View this message in context:
http://www.nabble.com/Way-to-prevent-page-versioning-for-a-request-in-1.3--tf3658645.html#a10248419
> 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
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
-------------------------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
