Hi Vincent Got busy for a while on other things, hence the delay. Yes, I agree that calling the server does not automatically create a session - under normal circumstances. However, we are using an application server (Atg Dynamo) which always creates a session object for every web request. Every http request passes through a servlet pipeline (a linked list of servlets) before the implementation class is given an opportunity to interact. By that time a session has already been created. It is the default behaviour, which can be switched off, but I can unfortunately not do that as the rest of the website depends on this behaviour.
I guess it is not reasonable to expect Cactus to accomodate for every web server's own ways of interacting with clients. I just thought that the changes I proposed could do no harm (checking if a session has been created, and if so invalidating it). Regards Jacques --- Vincent Massol <[EMAIL PROTECTED]> wrote: > Hi Jacques, > > See my other mail. Are you sure there are 3 sessions > per test created? > I'd say there is one at most. Calling the server > side does not > automatically result in a session, you need to call > getSession(true) to > create a session, right? > > Thanks > -Vincent > > > -----Original Message----- > > From: jacques [mailto:[EMAIL PROTECTED] > > Sent: 25 August 2003 16:06 > > To: [EMAIL PROTECTED] > > Subject: question wrt session creation when > running cactus from ant > > > > Hi there > > > > I am having problems with the amount of http > sessions > > that are created when cactus is invoked from ant. > It > > looks like for each test run ant (using the > <cactus> > > task) call the web server once, to check that it's > > running. Something like : > > > > > /cactification/ServletRedirector?Cactus_Service=RUN_TEST > > HTTP/1.1 > > > > Then, for each test method, 2 seperate http calls > are > > made. One to request the servlet redirector to > execute > > the test, and one to request the result. Something > > like : > > > > > /cactification/ServletRedirector?Cactus_TestMethod=testSetContentTypeHea > de > > > r&Cactus_TestClass=org.apache.cactus.sample.unit.TestHttpHeaders&Cactus_ > Au > > tomaticSession=false&Cactus_Service=CALL_TEST > > HTTP/1.1 > > and... > > > > > /cactification/ServletRedirector?Cactus_Service=GET_RESULTS > > HTTP/1.1 > > > > These 2 calls (and thus request objects) cause 2 > http > > sessions to be created on the application server. > Of > > the 2, I have access to one (the one that makes > the > > test call) and can invalidate it in the tearDown. > That > > leaves me with 1 redundant session (the one > associated > > with the result request). One session on the app > > server for each test method run. I have 276 test > > methods that I need to run, and only a 20 session > > developer license. My problem (and therefore my > > question) is quite obvious : How can I get access > to > > the request that's made in the second call, so > that I > > can call getSession(false).invalidate() on it ? > > > > Jacques > > > > > > > > > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Search - Faster. Easier. Bingo. > > http://search.yahoo.com > > > > > --------------------------------------------------------------------- > > 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] > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
