Hi Michael, I haven't looked at your other emails yet (still need some time) but what do you mean when you say "- obviously - the response is empty." ?
The GET_RESULTS service is supposed to always send back the result so the HTTP response cannot be empty. WRT to Session creation, it doesn't matter at all. The reason is that Cactus stores the test result in the servlet "application" scope, i.e. it is available during the whole lifetime of the servlet container to any request/session. -Vincent > -----Original Message----- > From: Michael Mattern [mailto:[EMAIL PROTECTED]] > Sent: 01 July 2002 15:33 > To: Cactus Users List > Subject: Re: Cactus and BroadVision 6.0? > > Hi, > > I've tracked down the problem as far as this: When Cactus posts its > "CALL_TEST" request, a new session is initiated. When it then posts the > "GET_RESULTS" request, another session is created, and - obviously - the > response is empty. > I think that I can now control the BV session handling - what is the > intended behavior: > - create a new session for each CALL_TEST/GET_RESULTS pair or > - create a new session when RUN_TEST is called? > > Thanks, > > Michael > > ________________________________________________________________________ __ > ____ > All inclusive! 100 MB Speicher, SMS 50% gunstiger, 32 MB Attachment-Gro?e, > Preisvorteile und mehr unter http://club.web.de/?mc=021104 > > > -- > To unsubscribe, e-mail: <mailto:cactus-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:cactus-user- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
