just make sure the cookie manager is in the test plan. that will make sure the sessionid is set for the current test.
peter On Fri, 20 Aug 2004 09:36:26 +1000, David Schulberg <[EMAIL PROTECTED]> wrote: > OK, My understanding of what is going on is slowly improving. > When I render the responses in HTML I see that I am not getting at the server > because it says that I am not logged on. The requests that I have recorded in my > usecase include a JSESSIONID associated with the logon session when I recorded the > use case. No doubt that JSESSIONID is not applicable to what I am trying to do when > I rerun the scenario. > > Do I have to include a recorded logon in my use case? Even then won't it have the > JSESSIONID value in the server requests that were recorded and aren't applicable to > a different session? > > DavidS > > > ###################################################################### > Attention: > > The information in this electronic mail is privileged and > confidential, intended only for use of the individual or entity named. > If you are not the intended recipient, any dissemination, copying or > use of the information is strictly prohibited. If you have received > this transmission in error, please delete it immediately from your > system and inform us via e-mail : [EMAIL PROTECTED] > > This e-mail has been scanned and cleared by MailMarshal > ###################################################################### > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
