That's correct! Thanks Carlos :-) -Vincent
> -----Original Message----- > From: Carlos Cortes [mailto:[EMAIL PROTECTED] > Sent: 25 August 2003 15:43 > To: Cactus Users List > Subject: RE: Question about Cactus test execution mechanism > > Hello Vahan, > > I am new to Cactus but the way I understood that description is that the > client JVM is started by the ServletTestRunner. Therefore, the > architecture is the same. > > Regards, > Carlos > > -----Original Message----- > From: Vahan Harput [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 24, 2003 2:44 PM > To: Cactus Users List > Subject: Question about Cactus test execution mechanism > > > Hi all, > > I have the following question about the the description of the Cactus > framework under http://jakarta.apache.org/cactus/how_it_works.html. > > If I understand this description correctly, there are two instances of the > test case and the test case instance on the client side and the redirector > proxy on the server side communicate with each other over HTTP connections > during test case execution. This description however seems to consider > only > the case where one starts the execution using a JUnit-Runner from the > client > side. It does not seem to consider the case where the execution is started > from the browser using the ServletTestRunner. I would like to know whether > the description of the working mechanism is still valid in this case. That > is, whether the test case is still instantiated twice and one of these > instances still communicates over HTTP connections with the redirector > proxies if we start the test case execution using ServletTestRunner. > > Best regards, > Vahan Harput > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
