i just verified that the framework appears to be behaving properly, so you need to stop flailing here and explain more about what's exactly going on. on a proper ajax request, it should impossible to get a backtrack error. if you're getting one, you're doing something wrong (or you've found some other bug in the frameworks, but i'm not seeing it if you did). so explain exactly what your action methods are doing, and what the structure of your page is. if you simplify your scenario, does it still happen? randomly doing things that don't make sense to you is a good way to cause worse problems. for instance, if you're doing just ajax requests, page refreshing on backtracking and page cache size don't do anything at all, so it's not going to make any diffrence. Similarly, just returning the context page from a backtrack error in an ajax update is a good way to whack out the rendering of your page (you're just going to jam the entire page into whatever area you're ajax updating).
Are you using the back button at all here, or just sitting on the same page and clicking ajax things? Are you opening other windows on the same session and navigating around? The only way for ajax to produce a backtrack error is if you blow the backtrack cache containing the page that is performing is the ajax request itself, which would imply that you're navigating around outside of the ajax requests. The other way you can do it is by killing your session (i think this results in the same error?) where you have a bogus request that is causing your session to terminate. ms On Dec 3, 2009, at 10:06 AM, Gustavo Pizano wrote: > HMM.. again it happened... I added the code bellow also into a another > WOActionResult method called by a AjaxSubmitButton in a AjaxSelectionList... > but stills it happened... now I dunno what to do. > > on desperate moments I just did this in the Application constructor: > > I dunno what exactly does.. and if it will do something about it... but now > Im in the phase.. "let's try it all" > setPageRefreshOnBacktrackEnabled(true); > setPageCacheSize(1); > > G. > On Dec 3, 2009, at 1:40 PM, [email protected] wrote: > >> You're the second person who has mentioned backtrack errors with new Ajax. >> Did something break? You should never get a backtrack error from an Ajax >> request. >> >> Sent from my iPhone >> >> On Dec 3, 2009, at 4:22 AM, "Gustavo Pizano"<[email protected]> >> wrote: >> >>> Hello all. >>> >>> In my app I have so AjaxUpdateContainers which gets updated when pressing >>> some AjaxSubmitButtons , (funny, :) ), now sometimes, when I, clicking the >>> submit butons, I get the you backtrack too far exception, it happens >>> randlmly, it can happen after clicking 10 times the button, or after >>> clicking 5, or sometimes it doesn't even happen. >>> >>> this is what Im doing at the end of the WOActionResult methods, >>> >>> >>> if (this.didBacktrack()){ >>> session().defaultEditingContext().revert(); >>> // handle and prepare to report errors >>> // this.errors.addObject("Unable to process page after back button was >>> pressed."); >>> return this.context().page(); >>> } >>> >>> I read it somewhere in the wiki, but it seems its not working.. >>> >>> Any suggestions.? >>> >>> thanks >>> >>> Gustavo >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com >>> >>> This email sent to [email protected] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
