Do you know if I'd be able to just grab the HybridUrlCodingStrategy and use it with the 1.3 beta 2 release, or if it depends on other enhancements made since beta2?
I ask because we are already stabilized and tested using wicket 1.3 beta2, and we launch in under 2 weeks, so I don't want to introduce a new Wicket version at this point if I can avoid it. Matej Knopp-2 wrote: > > Well, if you really have trouble with this, safest bet imho is mount > the page using HybridUrlCodingStrategy and make sure that the page is > delivered with Cache-Control: no-store header (set inside > Page.configureResponse). > > You need most recent 1.3 to be able to mount the page using > HybridUrlCodingStrategy. > > -Matej > > On 8/6/07, dukejansen <[EMAIL PROTECTED]> wrote: >> >> Did anything ever happen on this? Trying to resolve issues with Ajax on >> bookmarkable pages when I use back button to go back to previous >> bookmarked >> pages. Ajax URLs don't seem to include context for the pagemap, and so >> are >> being applied in context of most recent page, instead of the page they >> were >> actually on... >> >> >> Matej Knopp wrote: >> > >> > Hi, >> > >> > there's a small issue with ajax on bookmarkable pages. >> > I you do anything AJAX on bookmarkable page and then refresh it in >> > browser, new instance is created and you basically lose your state. >> > >> > I think there is a solution of this. The URL hash (part starting with >> #) >> > can be modified with javascript. So the ajax processing could append >> > something like >> > #<pagemap-name>:<page-id>:<version-id> to url. >> > >> > So the url would contain both page class and specification of concrete >> > page in pagemap. >> > >> > The RequestTargetResolverStrategy would check, if there is a hash in >> > url, and if so, it would try to take the specified page from pagemap. >> If >> > it founds the page and the class matches with the class in url, it >> would >> > display that page. Otherwise it would create new URL just like normal >> > bookmarkable URL would. >> > >> > If this worked well, it could be extended even for "normal" page URLs, >> > so the URLs could become "hybrid". They would point to specific page in >> > pagemap, but they would be also bookmarkable. >> > >> > >> > >> > -Matej >> > >> > Using Tomcat but need to do more? Need to support web services, >> security? >> > Get stuff done quickly with pre-integrated technology to make your job >> > easier >> > Download IBM WebSphere Application Server v.1.0.1 based on Apache >> Geronimo >> > >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >> > _______________________________________________ >> > Wicket-develop mailing list >> > [EMAIL PROTECTED] >> > https://lists.sourceforge.net/lists/listinfo/wicket-develop >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Ajax-on-pages-with-bookmarkable-URLs-tf1909909.html#a12009051 >> Sent from the Wicket - Dev mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Ajax-on-pages-with-bookmarkable-URLs-tf1909909.html#a12059163 Sent from the Wicket - Dev mailing list archive at Nabble.com.
