> -----Original Message----- > From: Manav Gupta [mailto:[EMAIL PROTECTED] > Sent: 04 July 2003 16:48 > To: 'Cactus Users List' (E-mail) > Subject: A 'How it works' question > > Hi, > > I have been trying to understand how Cactus works. I've gone through the > document http://jakarta.apache.org/cactus/how_it_works.html , but its not > clear from the document (at least to me), the order of execution of the > methods. > > 1. Are all 'beginXXX' methods executed at once at the client side? Or are > these executed in separate threads (and each thread then establishes a > connection to the server-side and waits for the response to come back and > then executes the corresponding 'endXXX' method)?
Hum... Is that so badly explained in the howto document? :-) Maybe you could provide a patch is that is so... ;-) The lifecycle is the following. For *EACH* test: Run begin() on client Run beginXXX() on client Connect to server run setUp() on server run testXXX() on server run tearDown() on server run endXXX() on server run end() on server > 2. If all 'beginXXX' methods are indeed executed one after the other (in a > loop), then what would be state of WebRequest object be? Would it contain > only the elements/properties set by the last 'beginXXX' method or will all > properties and attributes set by all 'beginXXX' methods be maintained? Cactus is a unit test framework and as such *every* test is independent of the other. Note: Not quite true if you put values in the application scope on the server side, but hey, we haven't found how to deal with this yet... > 3. If all 'beginXXX' methods are indeed executed in a loop, how can the > testXXX methods on the server-side expect to have a certain state (in the > usual web objects, such as Config, response and request, etc)? they are not executed in a loop.... -Vincent > > > Many Thanks, > M > > --------------------------------------------------------------------- > 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]
