Force page refresh after Ajax request completes?

Discussion:

dukejansen

2007-05-09 07:55:04 UTC

Anyone have any recommendations for how I would go about getting my Ajax
event handler method to trigger a refresh of the current page on the client
side after it is done with the Ajax request? My Ajax event handler needs to
first close the current modal window and then refresh the entire page.

I've tried:

ModalWindow.closeCurrent(target);
target.appendJavascript("window.location.reload()");

But I get the Javascript popup client side warning me that I'm navigating
away from a page while a modal window is still open. Seems like a bug. Is
there a better way to do this?

-Jason
--
View this message in context: http://www.nabble.com/Force-page-refresh-after-Ajax-request-completes--tf3714279.html#a10389905
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/

Eelco Hillenius

2007-05-09 08:47:59 UTC

Permalink

Is there a better way to do this?

Yep. Just call setResponsePage(MyPage.this) or
RequestCycle.get().setResponsePage or something similar. Only works in
1.3 I think.

Eelco

-------------------------------------------------------------------------
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/

Arnout Engelen

2007-05-09 08:52:39 UTC

Permalink

Post by Eelco Hillenius

Is there a better way to do this?

Yep. Just call setResponsePage(MyPage.this) or
RequestCycle.get().setResponsePage or something similar. Only works in
1.3 I think.

Wouldn't that open MyPage inside the ModalWindow, since the javascript
for closing the ModalWindow was added to the AjaxRequestTarget which
gets ignored because of the setResponsePage()?

Arnout

Eelco Hillenius

2007-05-09 09:42:48 UTC

Permalink

Ah. Maybe next time I'll try to acually read the whole email instead
of just the subject :) Sorry.

Matej, or anyone else with knowledge of modal windows... any ideas?

Eelco

Is there a better way to do this?
Yep. Just call setResponsePage(MyPage.this) or
RequestCycle.get().setResponsePage or something similar. Only works in
1.3 I think.
Wouldn't that open MyPage inside the ModalWindow, since the javascript for
closing the ModalWindow was added to the AjaxRequestTarget which gets
ignored because of the setResponsePage()?
Arnout
-------------------------------------------------------------------------
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
https://lists.sourceforge.net/lists/listinfo/wicket-user

Arnout Engelen

2007-05-09 09:51:47 UTC

Permalink

My Ajax event handler needs to first close the current modal window and then refresh the entire page. Is there a better way to do this?

I once worked around something like this by putting the redirect in the
windowClosedCallback of the ModalWindow. That was sufficient in our
case, but I too would be interested in some more enlightenment in this
area :).

Arnout

-------------------------------------------------------------------------
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/

Matej Knopp

2007-05-09 12:48:20 UTC

Permalink

There is a way that should also work in recent 1.x. To disable the
confirmation dialog you need to put this inside the page with modal
window:
<script type="text/javascript">
Wicket.Window.unloadConfirmation=false;
</script>

-Matej

Post by Arnout Engelen

My Ajax event handler needs to first close the current modal window and then refresh the entire page. Is there a better way to do this?

I once worked around something like this by putting the redirect in the
windowClosedCallback of the ModalWindow. That was sufficient in our
case, but I too would be interested in some more enlightenment in this
area :).
Arnout
-------------------------------------------------------------------------
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
https://lists.sourceforge.net/lists/listinfo/wicket-user

dukejansen

2007-05-09 18:50:23 UTC

Permalink

Yeah, but I don't want to disable that warning. That warning is valid if the
user really does try to navigate away while the modal is still being
displayed.

The problem is that I am actually closing the modal before I do the
redirect, so it shouldn't show the warning at all.

-Jason

Post by Matej Knopp
There is a way that should also work in recent 1.x. To disable the
confirmation dialog you need to put this inside the page with modal
<script type="text/javascript">
Wicket.Window.unloadConfirmation=false;
</script>
-Matej

My Ajax event handler needs to first close the current modal window and

then refresh the entire page. Is there a better way to do this?
I once worked around something like this by putting the redirect in the
windowClosedCallback of the ModalWindow. That was sufficient in our
case, but I too would be interested in some more enlightenment in this
area :).
Arnout
-------------------------------------------------------------------------
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
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
https://lists.sourceforge.net/lists/listinfo/wicket-user

--
View this message in context: http://www.nabble.com/Force-page-refresh-after-Ajax-request-completes--tf3714279.html#a10400468
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/

Matej Knopp

2007-05-09 19:33:52 UTC

Permalink

The problem is that when setResponsePage() is called, no appended
Javascript is evaluated. In fact, wicket doesn't process the ajax
response at all. Just sets window.location.

-Matej

Post by dukejansen
Yeah, but I don't want to disable that warning. That warning is valid if the
user really does try to navigate away while the modal is still being
displayed.
The problem is that I am actually closing the modal before I do the
redirect, so it shouldn't show the warning at all.
-Jason

My Ajax event handler needs to first close the current modal window and

--
View this message in context: http://www.nabble.com/Force-page-refresh-after-Ajax-request-completes--tf3714279.html#a10400468
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
https://lists.sourceforge.net/lists/listinfo/wicket-user

dukejansen

2007-05-10 16:58:16 UTC

Permalink

Yup. That's why I was trying to do it using
target.appendJavascript("window.location.reload()") instead of doing the
setResponsePage server side...? Since I'm appending that Javascript AFTER
the 'close modal window' call, it seems like it should be able to close the
modal window client side, THEN call my javascript to refresh the page,
without the warning, since the modal has been closed.. ?

Post by Matej Knopp
The problem is that when setResponsePage() is called, no appended
Javascript is evaluated. In fact, wicket doesn't process the ajax
response at all. Just sets window.location.
-Matej

My Ajax event handler needs to first close the current modal window

and