Re: Initial page - state question
Hi Igor, The same happens now if i use Bookmarkable PageLinks (maybe i miss-configured something) Example: http://localhost:8080/user/id/4711 Is it always nessesary to make the redirect or only at the first page-access? Thanks Jens Am 30.12.2009 17:48, schrieb Igor Vaynberg: while not being an official solution it works. -igor On Wed, Dec 30, 2009 at 8:09 AM, Jens Zastrowm...@jens-zastrow.de wrote: Hi wicket-experts, If i access my wicket page by an url containing the wicket-page version-informations all ajax-modificatins (tree-selections, form-input) are still available after pressing the 'reload' button. Example: http://localhost:8080/?wicket:interface=:2 Unfortunly this does hold for the first-page of my app, which is invoked by a plain url http://localhost:8080/ - without any page-version information. The 'reload' button now has the effect that all the ajax-modifications are gone. I know why that happens and that the behavior is correct. But is there a way the solve this in a wicket-way? My current workaround is a redirect which - i guess - is not the official solution to this? Thanks Jens - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- dipl. inform jens zastrow phone | +49.152.04840108 mail | m...@jens-zastrow.de web | http://jens-zastrow.de xing | http://www.xing.com/profile/Jens_Zastrow - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Initial page - state question
Hi wicket-experts, If i access my wicket page by an url containing the wicket-page version-informations all ajax-modificatins (tree-selections, form-input) are still available after pressing the 'reload' button. Example: http://localhost:8080/?wicket:interface=:2 Unfortunly this does hold for the first-page of my app, which is invoked by a plain url http://localhost:8080/ - without any page-version information. The 'reload' button now has the effect that all the ajax-modifications are gone. I know why that happens and that the behavior is correct. But is there a way the solve this in a wicket-way? My current workaround is a redirect which - i guess - is not the official solution to this? Thanks Jens - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Initial page - state question
while not being an official solution it works. -igor On Wed, Dec 30, 2009 at 8:09 AM, Jens Zastrow m...@jens-zastrow.de wrote: Hi wicket-experts, If i access my wicket page by an url containing the wicket-page version-informations all ajax-modificatins (tree-selections, form-input) are still available after pressing the 'reload' button. Example: http://localhost:8080/?wicket:interface=:2 Unfortunly this does hold for the first-page of my app, which is invoked by a plain url http://localhost:8080/ - without any page-version information. The 'reload' button now has the effect that all the ajax-modifications are gone. I know why that happens and that the behavior is correct. But is there a way the solve this in a wicket-way? My current workaround is a redirect which - i guess - is not the official solution to this? Thanks Jens - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
