D'oh - I've been assuming that setup and tearDown were the client side calls, and the beginXXX endXXX were the serverside calls.
Now it makes perfect sense :-) Kevin Jones Developmentor www.develop.com > -----Original Message----- > From: Nicholas Lesiecki [mailto:[EMAIL PROTECTED]] > Sent: 31 October 2001 16:05 > To: Cactus Users List > Subject: RE: Order of calls > > > Kevin, > > The reason is that the setUp and tearDown are executed on the server side. > The begin and end methods are executed client side. Thus the begin and end > methods deal with the request before it hits the server and the response > from the server respectively. Thus they execute *around* the code which > executes on the server side. > > See: > http://jakarta.apache.org/cactus/how_it_works.html > > For details on how Cactus works. > > Cheers, > > Nick > > -----Original Message----- > From: Kevin Jones [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 31, 2001 7:02 AM > To: Cactus-User > Subject: Order of calls > > > Is there a reason that the testing methods are called in the > order they are. > > It would seem reasonable in my ignorance that the order should be (for a > POST) > > setUp -> beginPostMethod -> doPost ->endPostMethod -> tearDown > > But it actually goes > > beginPostMethod -> setUp -> doPost -> tearDown -> endPostMethod > > I know there must be a good reason for this - I just wondered what it was? > > Kevin Jones > Developmentor > www.develop.com > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
