Chuck: > You have bad (broken, invalid, call it what you want) in your application somewhere. > Override dispatchRequest in Application and log out each incoming request.uri().
Thanks for the suggestion. Did that and didn't find anything unusual in the log. Things were getting a bit ugly - so I restructured, simplified and cleaned up the components and code (which was way overdue anyway). That got rid of the backtracking error. :-) --JSt P.S: Thanks to others for their suggestions as well. On Mon, Nov 24, 2008 at 6:00 PM, Chuck Hill <[EMAIL PROTECTED]>wrote: > > On Nov 24, 2008, at 2:52 PM, J Stephanos wrote: > > > Storing session IDs as cookies and then blocking cookies perhaps? >> >> The wosid is in the cookie file. And cookies are not being blocked. >> >> --JSt >> >> On Mon, Nov 24, 2008 at 1:27 PM, Ramsey Lee Gurley <[EMAIL PROTECTED]> >> wrote: >> Storing session IDs as cookies and then blocking cookies perhaps? >> >> Ramsey >> >> On Nov 24, 2008, at 12:50 PM, J Stephanos wrote: >> >> >Are your Application and Session classes extending ERXApplication and >>> ERXSession? >>> >>> Yes I am extending ERXApplication and ERXSession. >>> >>> --JSt >>> >>> On Mon, Nov 24, 2008 at 12:31 PM, David LeBer < >>> [EMAIL PROTECTED]> wrote: >>> >>> On 24-Nov-08, at 12:25 PM, J Stephanos wrote: >>> >>> You backtracked too far. >>> The application backtracking limit of 30 has been exceeded. >>> >>> Here is the scenario: >>> • I have a simple form with AjaxSubmitButton (Choices >>> sub-component) >>> • On submit it is to show 2 report formats. I use AjaxTabPanel to >>> display the 2 report types. (Reports sub-component, which 2 tabs, Summary & >>> Detail) >>> Summary is the selected tab. >>> >>> • On the first submit, the selected tab displays the contents >>> correctly. Any subsequent click on these two tabs, results in the >>> backtracking error even though I am not clicking on the back button. >>> What am I doing wrong? >>> >>> Don't know. >>> >>> Are your Application and Session classes extending ERXApplication and >>> ERXSession? >>> >> > I will pick door number three. You have bad (broken, invalid, call it what > you want) in your application somewhere. This makes the browser send a > request that creates a new session (and cookies), which replaces the real > session. > > Override dispatchRequest in Application and log out each incoming > request.uri(). > > Chuck > > > -- > Chuck Hill Senior Consultant / VP Development > > Practical WebObjects - for developers who want to increase their overall > knowledge of WebObjects or who are trying to solve specific problems. > http://www.global-village.net/products/practical_webobjects > > > > > > >
_______________________________________________ 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]
